AI agents call delete_path to permanently remove resources in Allcanuse — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Destructive category is appropriate because deletion of files/paths is irreversible and cannot be undone. The tool operates on the local filesystem of a Windows/Linux system, giving it wide blast radius. Critical severity reflects that an AI agent given this tool without proper safeguards could permanently destroy critical system files, user data, or application configurations.
From the tool's definition Tool name is 'delete_path' with no description provided. The name explicitly indicates deletion functionality.
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 Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_path:
{
"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.
Free to start. No card required.
delete_path. It is categorised as a Destructive tool in the Allcanuse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Allcanuse 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 Allcanuse. 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 Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.