This record as markdown: /tools/54yyyu-code-mcp/delete-path.md
What delete_path does on Code
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.
Why delete_path is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs delete_path safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_path, this is the rule to start with:
delete_path is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Code, apply this rule, and every delete_path call is checked against it from then on.
Questions about delete_path
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.
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.
delete_path is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
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.
More on Code, and thousands of servers like it.
Across the catalogue