Protocol
Put approval immediately before the high-impact action
Approval at the start of a long plan is not approval of the action the plan eventually invented.
Before you use it
- Use when
- An agent can send, delete, publish, purchase, merge, transfer or otherwise create consequential external effects.
Keep this limit in mind
- Human approval can become a rubber stamp if prompts are frequent, vague or hide relevant consequences.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Insert human approval at the boundary where the consequential action is fully specified. Show the target, important parameters and expected effect. After approval, execute that bounded action rather than giving the agent blanket permission for whatever comes next.
Steps
- The reviewer can tell what will change before accepting the action.
An example
Before an agent merges a pull request, show the repository, branch, PR, checks and exact merge operation rather than asking for generic 'GitHub access.'
Check your result
The reviewer can tell what will change before accepting the action.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingPut approval immediately before the high-impact action
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaBound how much damage one agent run can do
Evidence and sources
OWASP recommends human approval before high-impact agent actions are taken.
Approval is useful only when the reviewer can see the consequential action and relevant context rather than clicking through a vague confirmation.
LLM06:2025 Excessive Agency · Require user approval
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.