delete_path

A destructive tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp

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/ra1nyxin-allcanuse-mcp/delete-path.md

WHAT IT DOES

What delete_path does on Allcanuse

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.

RISK

Why delete_path is rated Critical

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_path safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allcanuse, 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 Hidden

delete_path 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_path"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_path

What does the delete_path tool do? +

delete_path is a destructive tool on the Allcanuse MCP server. 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.

How do I enforce a policy on delete_path? +

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.

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 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.

KEEP EXPLORING

More on Allcanuse, and thousands of servers like it.

This server

All 130 Allcanuse tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →