An approval gate pauses the agent before an action that needs human permission. The prompt should show the exact command or operation, why it is needed, and what resources it can affect. The person can allow it once, allow a narrow class of similar actions, or reject it.
Gates reduce the chance that a mistaken or malicious instruction causes damage. Use them for file writes outside scope, package installation, network access, credentials, production systems, and destructive commands. Avoid training users to approve everything by making low-risk actions safe by default and prompts specific. Approval is not proof that the action is correct; it is a decision to permit a known impact within the larger review process.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
