delete_ai_key

Remove a stored AI provider API key

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/delete-ai-key.md

WHAT IT DOES

What delete_ai_key does on EasyBits

AI agents call delete_ai_key to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_ai_key is rated Critical

Irreversibly deletes API credentials; cannot be undone without re-generating the key.

From the tool's definition Remove a stored AI provider API key

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_ai_key safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_ai_key, this is the rule to start with:

delete_ai_key Hidden

delete_ai_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every delete_ai_key call is checked against it from then on.

FAQ

Questions about delete_ai_key

What does the delete_ai_key tool do? +

Remove a stored AI provider API key. It is categorised as a Destructive tool in the EasyBits 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_ai_key? +

Register the EasyBits MCP server in PolicyLayer and add a rule for delete_ai_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 EasyBits. Nothing to install.

What risk level is delete_ai_key? +

delete_ai_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_ai_key? +

Yes. Add a rate_limit block to the delete_ai_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_ai_key completely? +

Set action: deny in the PolicyLayer policy for delete_ai_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_ai_key? +

delete_ai_key is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → Critical-risk tools on this server →

Across the catalogue

delete_ssh_key on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →