01 / The operating case
What changes in a real workflow?
An operator removes a finance agent’s access while an MCP task is waiting for human input, then the task resumes.
- 01Client / task
- 02MCP server
- 03Tool call + arguments
- 04Downstream effect
02 / Decision contract
What the executor must check
Recheck issuer token state and task grant before consequential continuation; invalidate local decisions and define what happens to already-started effects.
03 / Failure and evidence
What goes wrong, and what can be proven?
A still-open session is treated as a continuing grant after the originating task is cancelled.
Record revocation time, session and task state, resumed call decision and any in-flight outcome.
04 / Canonical scope
Why this reference stands alone
General authority revocation covers the grant graph; this page covers MCP session and task continuation.
Protocol or attack trace
Resume after withdrawal
Grant G is revoked while an MCP task waits for elicitation. Worker resumes later with an open session.
Resume tools/call after G revocation; executor must deny the consequential step.
Primary references