Revoke an API key
AI agents call charisma_revoke_api_key to permanently remove resources in Stacks AI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking an API key destroys access credentials irreversibly. Once revoked, the key cannot be restored without re-issuing a new one. This is a destructive operation with potential to disrupt service access. While not data deletion, it is a permanent state change that cannot be undone, placing it in the Destructive category rather than Write.
From the tool's definition Tool name contains 'revoke' and description states 'Revoke an API key' — revocation is an irreversible action that permanently disables authentication credentials and cannot be undone.
Attacks that exploit this kind of access
Revoke an API key. It is categorised as a Destructive tool in the Stacks AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for charisma_revoke_api_key: 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 Stacks AI MCP Server. Nothing to install.
charisma_revoke_api_key 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 charisma_revoke_api_key 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 charisma_revoke_api_key. 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.
charisma_revoke_api_key is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →