Cancel an in-flight OAuth authorization-code session by state after the user abandons the flow.
AI agents call oauth.cancel to permanently remove resources in Executor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an OAuth session is an irreversible action that terminates the authorization flow; the session cannot be resumed once cancelled. While the blast radius is limited (only the specific auth session is destroyed, not broader data), the action is not undoable, placing it in the Destructive category rather than Write.
From the tool's definition Cancel an in-flight OAuth authorization-code session by state after the user abandons the flow.
Documented attack patterns abuse exactly the kind of access oauth.cancel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Executor, and nothing reaches the server without passing your rules. This is the rule we recommend for oauth.cancel:
{
"version": "1",
"default": "deny",
"hide": [
"oauth.cancel"
]
}oauth.cancel disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel an in-flight OAuth authorization-code session by state after the user abandons the flow. It is categorised as a Destructive tool in the Executor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Executor MCP server in PolicyLayer and add a rule for oauth.cancel: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Executor. Nothing to install.
oauth.cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the oauth.cancel rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for oauth.cancel. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
oauth.cancel is provided by the Executor MCP server (rhyssullivan/executor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Executor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Executor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.