delete_api_key

Delete an API key by ID

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/delete-api-key.md

WHAT IT DOES

What delete_api_key does on instantKOM MCP Server

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

RISK

Why delete_api_key is rated Critical

Deleting an API key is an irreversible operation that permanently removes authentication credentials. This action cannot be undone and will immediately break any integrations or applications relying on that key. The blast radius depends on what systems use the deleted key, but loss of API access can disrupt operations.

From the tool's definition Tool name is 'delete_api_key' and description states 'Delete an API key by ID'. The verb 'Delete' combined with the irreversible nature of removing API credentials indicates a destructive action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_api_key safely

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

delete_api_key Hidden

delete_api_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_api_key"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_api_key

What does the delete_api_key tool do? +

Delete an API key by ID. It is categorised as a Destructive tool in the instantKOM 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 instantKOM 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 instantKOM 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 instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on instantKOM MCP Server, and thousands of servers like it.

This server

All 245 instantKOM MCP Server 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 →web3_revoke_key on 0xarchive → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →