delete_api_key

THE RISK

Critical Risk

Why delete_api_key needs a policy

Deleting an API key is an irreversible destructive action that permanently removes access credentials. While not as severe as data deletion, it has significant blast radius: a mistaken deletion could revoke legitimate service access, break integrations, or lock users out of AnythingLLM functionality.

From the tool's definition Tool name explicitly states 'delete' combined with 'api_key'. Description confirms 'Delete an API key' - a permanent, irreversible action that removes authentication credentials.

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

POLICY

How to control delete_api_key

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_api_key"
  ]
}

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

Create a free account and register AnythingLLM MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AnythingLLM MCP Server tools

Destructive clear_chat_history Clear all chat history for a workspace Destructive delete_agent Delete an agent Destructive delete_document Delete a document from a workspace Destructive delete_user Delete a user Destructive delete_workspace Delete a workspace Execute initialize_anythingllm Initialize the AnythingLLM client with API credentials Execute invoke_agent Invoke an agent with input Execute chat_with_workspace Send a chat message to a workspace

All 38 AnythingLLM MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in AnythingLLM MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_api_key

What does the delete_api_key tool do? +

Delete an API key. It is categorised as a Destructive tool in the AnythingLLM MCP Server 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 delete_api_key? +

Register the AnythingLLM 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 AnythingLLM MCP Server. Nothing to install.

What risk level is delete_api_key? +

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.

Can I rate-limit delete_api_key? +

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.

How do I block delete_api_key completely? +

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.

What MCP server provides delete_api_key? +

delete_api_key is provided by the AnythingLLM MCP Server MCP server (raqueljezweb/anythingllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AnythingLLM MCP Server tool call.

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

CHECK YOUR STACK →