revoke_token
[Account Management API 2] Revokes an access token and, if any, a refresh token in accordance with [RFC7009](https://datatracker.ietf.org/doc/html/rfc7009). Confidential clients must either follow Basic authentication scheme or provide credentials in the request body. Public clients must provide ...
This record as markdown: /tools/acronis-platform-mcp/revoke-token.md
What revoke_token does on Acronis Platform
AI agents call revoke_token to permanently remove resources in Acronis Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | — | Request body (application/x-www-form-urlencoded) |
headers | object | — | Request headers |
Parameters from the server's own tool schema.
Why revoke_token is rated Critical
An AI agent that decides to call revoke_token doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Acronis Platform is gone. There is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs revoke_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Acronis Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_token, this is the rule to start with:
revoke_token is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Acronis Platform, apply this rule, and every revoke_token call is checked against it from then on.
Questions about revoke_token
[Account Management API 2] Revokes an access token and, if any, a refresh token in accordance with [RFC7009](https://datatracker.ietf.org/doc/html/rfc7009). Confidential clients must either follow Basic authentication scheme or provide credentials in the request body. Public clients must provide client_id in the request body. If access_token revocation is requested, the refresh token, if any, issued together with provided access token will also be revoked. If refresh_token revocation is requested…. It is categorised as a Destructive tool in the Acronis Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_token accepts 2 parameters: body, headers. The full parameter table on this page comes from the server's own tool schema.
Register the Acronis Platform 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 Acronis Platform. Nothing to install.
revoke_token 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 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.
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.
revoke_token is provided by the Acronis Platform MCP server (@acronis-platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Acronis Platform, and thousands of servers like it.
Across the catalogue