Mission-Bound OAuth
A multi-part framework proposed by IAM practitioner Karl McGuinness for scoping an AI agent's OAuth-issued authority to a specific, human-approved "Mission" — a bounded, versioned task grant — rather than a broad standing scope.
In our briefings
The claim each of the newest briefings on Mission-Bound OAuth would have you leave with.
A person's approved request is not, by itself, authority an agent can be held to, McGuinness argues, and relatively few deployments perform the step that would make it one. That step converts approved intent into a bounded authority artifact an enforcement point can evaluate. By his account, many systems instead fall into one of five patterns: scope enumeration, app-local mapping, LLM-generated requests, broad standing authority with prompt discipline, or a formal policy language. He says the most common land in the third or fourth, and that where nothing makes the conversion, the agent's own judgment becomes the effective policy engine. This is one author's argument, but two production designs we have read fit it. Uber's agent tokens carry the full chain of who asked through every hop, and Sierra's gateway runs interactive agent work as the user, with that person's permissions. In our reading, neither records what the person approved.
A user's approved request is not yet authority an agent can be held to, and most deployments skip that stepBI-FIND-2026-0202
The author of Mission-Bound OAuth has argued himself out of it. McGuinness's closing verdict is that a durable, approvable record of what an agent may do, the mission, is the right object, and that the authorization server is the wrong place to keep it: his test is that an architecture which still makes sense with the protocol removed has found the wrong home, and a mission makes as much sense under a job scheduler or a tool broker as under OAuth. The replacement he sketches is a separate Mission Authority Service that authorization servers, gateways and schedulers consult, with per-step credentials and no standing authority as the stricter fallback; a note added after publication says the design has since moved on to a draft family and a handbook of his own.
Mission-Bound OAuth's author now says the mission object does not belong in OAuthBI-FIND-2026-0223
Cited in 2 briefings
Every briefing that discusses this term, newest first.
- A user's approved request is not yet authority an agent can be held to, and most deployments skip that step
Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 17, 2026
- Mission-Bound OAuth's author now says the mission object does not belong in OAuth
Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 15, 2026