Critical Risk →

revoke_token

Revoke an issued access_token or refresh_token at POST /v1/token/revoke. Use to terminate a recurrence mandate or after card-token deletion. Form-encoded; expects a signed JWT client_assertion.

How to control revoke_token ↓

What revoke_token does on Mcp Ap2

AI agents call revoke_token to permanently remove resources in Mcp Ap2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why revoke_token needs a policy

Revoking a token or terminating a recurrence mandate is irreversible — once revoked, the token cannot be reinstated and ongoing payment authorizations (mandates) are permanently cancelled. This maps to Destructive. The blast radius is high because misuse could terminate legitimate payment flows or subscriptions.

From the tool's definition 'Revoke an issued access_token or refresh_token', 'terminate a recurrence mandate or after card-token deletion'

Documented attack patterns abuse exactly the kind of access revoke_token gives an agent:

How to control revoke_token

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for revoke_token:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_token"
  ]
}

revoke_token disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about revoke_token

What does the revoke_token tool do? +

Revoke an issued access_token or refresh_token at POST /v1/token/revoke. Use to terminate a recurrence mandate or after card-token deletion. Form-encoded; expects a signed JWT client_assertion. It is categorised as a Destructive tool in the Mcp Ap2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on revoke_token? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for revoke_token: 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 Mcp Ap2. Nothing to install.

What risk level is revoke_token? +

revoke_token is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revoke_token? +

Yes. Add a rate_limit block to the revoke_token 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.

How do I block revoke_token completely? +

Set action: deny in the PolicyLayer policy for revoke_token. 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.

What MCP server provides revoke_token? +

revoke_token is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.