Critical Risk →

delete_path

Permanently delete a file or directory (recursively if directory).

How to control delete_path ↓

What delete_path does on PythonAnywhere MCP Server

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

Critical Risk

Why delete_path needs a policy

This tool irreversibly deletes files and directories without recovery options. It is Destructive rather than Execute because the primary action is data removal, not command execution. The high severity reflects that an AI agent with access could inadvertently or maliciously wipe application files, configurations, or entire project directories on PythonAnywhere.

From the tool's definition Tool description explicitly states 'Permanently delete a file or directory (recursively if directory).' The words 'Permanently delete' and 'recursively' indicate irreversible removal of data with no undo capability.

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

How to control delete_path

PolicyLayer is an MCP gateway — it sits between your AI agents and PythonAnywhere MCP Server, 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 PythonAnywhere MCP Server — 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.

Related tools and policies

Go deeper

Questions about delete_path

What does the delete_path tool do? +

Permanently delete a file or directory (recursively if directory). It is categorised as a Destructive tool in the PythonAnywhere 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_path? +

Register the PythonAnywhere MCP Server 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 PythonAnywhere MCP Server. 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 PythonAnywhere MCP Server MCP server (pythonanywhere/pythonanywhere-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 PythonAnywhere MCP Server tool call.

Start from PythonAnywhere MCP Server, 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.

20 PythonAnywhere MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.