delete-tool

THE RISK

Critical Risk

Why delete-tool needs a policy

The tool performs an irreversible deletion operation on server tools. While the blast radius is scoped to tool availability rather than data, the operation is permanent and aligns with the Destructive category definition.

From the tool's definition Tool name 'delete-tool' with description 'Delete a tool' indicates irreversible removal of a tool from the server. This is a destructive operation that cannot be undone and affects the server's available functionality.

Documented attack patterns abuse exactly the kind of access delete-tool gives an agent:

POLICY

How to control delete-tool

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-tool"
  ]
}

delete-tool 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 Dynamic 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 Dynamic MCP Server tools

Destructive delete-prompt Delete a prompt from the system Destructive delete-user Delete a user Destructive remove-user Remove (delete) a user by email. This action is irreversible. You must confirm with the us Write reset-api-key Reset a user Write add-prompt Add a new prompt to the system Write add-user Add a new user Write hide-tool Hide one or more tools for the current user Write share-tool Share a tool with another user (adds to their sharedTools array)

All 18 Dynamic 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 Dynamic 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-tool

What does the delete-tool tool do? +

Delete a tool. It is categorised as a Destructive tool in the Dynamic 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-tool? +

Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for delete-tool: 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 Dynamic MCP Server. Nothing to install.

What risk level is delete-tool? +

delete-tool 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-tool? +

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

Set action: deny in the PolicyLayer policy for delete-tool. 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-tool? +

delete-tool is provided by the Dynamic MCP Server MCP server (scitara-cto/dynamic-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 Dynamic MCP Server tool call.

Start from Dynamic 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 →