Critical Risk →

delete_webapp

delete_webapp

How to control delete_webapp ↓

What delete_webapp does on PythonAnywhere MCP Server

AI agents call delete_webapp 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_webapp needs a policy

Deleting a webapp is an irreversible operation that removes application configurations, deployments, and associated resources. This cannot be undone without manual restoration and causes loss of service. The high severity reflects significant blast radius if an AI agent mistakenly targets a production webapp.

From the tool's definition Tool name is 'delete_webapp' which explicitly performs a delete operation on a webapp resource. The sibling tool 'delete_website' and 'delete_path' on this server confirm the pattern of destructive deletion tools.

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

How to control delete_webapp

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_webapp:

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

delete_webapp 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_webapp

What does the delete_webapp tool do? +

delete_webapp. 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_webapp? +

Register the PythonAnywhere MCP Server MCP server in PolicyLayer and add a rule for delete_webapp: 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_webapp? +

delete_webapp 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_webapp? +

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

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

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