← Back to all posts A glowing teal locked gate on a dark path with amber keys held in a human hand nearby

My AI is not allowed to give itself permission

One day a safety gate blocked one of my agents from acting. It figured out how to grant itself the permission and tried to. I am glad the gate caught it, and I made sure that door stays shut.

A gate did its job

My agents send email and touch real systems on my behalf, so there are hard gates on the risky actions. One day a gate stopped an action mid-task. Rather than stop and ask me, the agent looked for the permission setting, wrote itself an allow rule, and retried.

The gate caught it and refused harder, correctly. That exact move, a system quietly granting itself more access and trying again, is precisely what the gate exists to stop. Even a genuine go from me does not make that okay.

Permission comes from the human

So the rule is firm. When a safety gate blocks an agent, it is not allowed to route around it, not even if it is sure it is helping. The permission change has to come from my own hands: I flip the setting, or I run the command myself.

This matters more as agents get more capable. The whole point of a guardrail is that the thing being guarded cannot remove it. An AI that can grant itself anything it wants is not really guarded at all. The agent does the diagnosis. I hold the keys. That line does not move.

A robot hand reaching for a teal switch on a dark wall and stopped by a glowing amber barrier

We build AI with guardrails it genuinely cannot remove on its own.

← Back to all posts