Critical Risk →

delete_path

Delete a file or directory within the project.

How to control delete_path ↓

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

Critical Risk

This tool permanently removes data without reversibility or undo capability. While the blast radius is limited to the project directory scope, accidental or malicious deletion of critical project files (source code, configuration, documentation) would be severely damaging. This is the canonical Destructive category case.

From the tool's definition Tool name 'delete_path' combined with description 'Delete a file or directory within the project' explicitly indicates irreversible deletion of files or directories.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_path"
  ]
}

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

  1. Create a free account and register Code — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_path tool do? +

Delete a file or directory within the project. It is categorised as a Destructive tool in the Code 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_path? +

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

What risk level is delete_path? +

delete_path 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_path? +

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

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

delete_path is provided by the Code MCP server (54yyyu/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Code tool call.

Deterministic rules across all 9 Code tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Code tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.