Revoke (delete) an API token by id.
AI agents call revoke_api_token to permanently remove resources in QR Forge MCP server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking an API token is a destructive action that permanently invalidates authentication credentials and cannot be undone. While not directly a data deletion, it irreversibly removes access rights and security materials. This qualifies as Destructive rather than Write because the operation cannot be reversed—a revoked token cannot be restored to its previous state without manual re-creation.
From the tool's definition Revoke (delete) an API token by id. The verb 'revoke' combined with 'delete' indicates an irreversible operation that destroys access credentials.
Attacks that exploit this kind of access
Revoke (delete) an API token by id. It is categorised as a Destructive tool in the QR Forge MCP server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QR Forge MCP server MCP server in PolicyLayer and add a rule for revoke_api_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 QR Forge MCP server. Nothing to install.
revoke_api_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_api_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_api_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_api_token is provided by the QR Forge MCP server MCP server (jkolarov/qrforge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →