Approving everything means catching nothing
Making a person approve every AI agent action feels safe. It is not. Reviewers tire, and the risky action slips through. Approve by risk instead.
Abhijit Chatterjee Chattopadhyay

If a person approves everything your AI agent does, nobody is checking anything. It is the safest-sounding rule for agents, and the one most likely to let the bad action through.
Why it fails
Picture the reviewer on day one. They read every request carefully. By week three, there are two hundred a day, almost all fine, and they click approve.
AWS puts it plainly in its Trust in Depth (opens in a new tab) guidance: as agents take on more work, "human approvals pile up and review fatigue sets in. People asked to check everything stop catching the things that matter."
So you pay twice. The agent waits on people, and the people stop protecting you.
Limits belong outside the agent
The fix is not more trust in the agent. It is moving the limits out of it.
A prompt that says "never spend more than $100" is a request. A payment service that refuses anything over $100 is a limit. AWS makes the same point. Put the boundaries in the environment around the agent, because, as they put it, "it cannot turn off a control it does not run".
Check by rule, ask by risk
Sort every action your agent can take into one of three groups:
- Blocked by rule. Things it must never do. Remove the tool or the permission, so it cannot.
- Checked by rule. Things a system can verify: within budget, right customer, right format. Let it act, and let the check decide.
- Asked by risk. Costly, hard to undo, or genuinely ambiguous. These, and only these, go to a person.
In that picture, your reviewers now see ten requests a day instead of two hundred, and every one deserves their attention.
Watch what it did
Green dashboards are not proof. As AWS notes, "a healthy system is not the same as a successful task". Keep a trace of what the agent saw, what it called and what it decided, and read the ones that went wrong.
Do this today
- Count how many approvals each reviewer handles per day, and how many they rejected last month.
- If the rejection rate is near zero, that queue is a rubber stamp, not a control.
- Move each approved-every-time action into "checked by rule".
- Keep people for the actions that are costly or hard to undo.
Your next step
I write one practical note like this every day. Sign up just below to get them by email.
Drafted with AI help, edited and approved by me.