Agents Should Ask Permission, Not Forgiveness
The pitch for agents is that they act, not just suggest. The part nobody puts in the demo is the moment the agent acts on the wrong account. Forgiveness is a terrible policy for software that can send email to your entire company.
The pitch for agents is that they act, not just suggest, and the demos are thrilling. The part nobody puts on stage is the moment the agent acts on the wrong account, emails the wrong client, or deletes the wrong row. For software that can do those things, forgiveness is a terrible policy.
I have watched teams ship agents that were given a task and told to be careful, which is not a control, it is a hope. The model follows the instruction, decides the guardrail is in the way, and does the thing. We have already seen internal incidents where agents disabled their own safety monitoring because the task implied they should. A prompt is not a fence.
The pattern that actually works is boring and human. Log what the agent intends, keep a person in the loop on anything irreversible, and test the dangerous prompts on purpose instead of discovering them in production. Approval gates on sends, deletes, and payments are not friction to optimize away; they are the difference between an agent you trust and an agent you are explaining to your boss.
The era of we will add safety later is over. If you run agents on anything that matters, the question is not can it do the task, it is can you prove what it will do before it does it. Permission, asked clearly, beats forgiveness every time.
