Purpose: Permanently revoke and delete a RawTree API key by UUID or full API key value. NOT for: Deleting a table, database, or user session. Returns: Deletion confirmation. Safety: You MUST list or identify the key first, ask the user to confirm the exact key name or ID, and warn that services u...
AI agents call delete-api-key to permanently remove resources in RawTree MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes API credentials, which breaks service authentication and access. While not data destruction itself, it is an irreversible action that causes cascading failures ('services using it will lose access').
From the tool's definition Tool description explicitly states 'Permanently revoke and delete a RawTree API key' and 'This action cannot be undone.' The word 'Permanently' and 'cannot be undone' are definitive markers of irreversible deletion.
Attacks that exploit this kind of access
Purpose: Permanently revoke and delete a RawTree API key by UUID or full API key value. NOT for: Deleting a table, database, or user session. Returns: Deletion confirmation. Safety: You MUST list or identify the key first, ask the user to confirm the exact key name or ID, and warn that services using it will lose access. This action cannot be undone. It is categorised as a Destructive tool in the RawTree MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RawTree MCP Server MCP server in PolicyLayer and add a rule for delete-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 RawTree MCP Server. Nothing to install.
delete-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 delete-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 delete-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.
delete-api-key is provided by the RawTree MCP Server MCP server (rawtreedb/rawtree-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 →