Confused Deputy
The confused deputy problem is a party with authority being tricked into misusing it by a party without authority. In a multi-agent system, the deputy is a supervisor agent that mints credentials and dispatches work, and the trick arrives in a worker's output after the worker read something hostile.
What it means
The supervisor holds the power: it mints credentials, chooses what runs next and speaks to the human. The worker holds less power but touches untrusted data: web pages, files, tool output. If a worker’s output can influence the supervisor’s decisions, anyone who can plant text in a page the worker reads has a path to the supervisor’s authority. The worker is the deputy. The supervisor is confused.
The one rule that follows: authority decisions must never depend on worker-supplied text. A worker’s return value is untrusted data even when the worker is yours, because the worker may have been hijacked by what it read.
In Proof Protocol
The Jailed Canary Protocol’s bait is built on this mechanism. A bad canary is a lure that causes harm only if obeyed. JC-04 Execution (obeyed a canary instruction outside policy), JC-06 Propagation (forwarded it to another agent) and JC-10 Conspiracy name the conduct that follows a confused deputy down the chain. See Offense Codes.
The harder case, in which every individual act is inside policy but the decision to widen a grant was caused by untrusted input, is an open item for the specification family.
Related terms
- Agent Boundary
- Capability Token
- Jailed Canary Protocol (No Bros Jail Mode)
- Offense Codes (JC-01 to JC-10)