Critical Risk →

drive__delete

Delete a file or folder from Proton Drive

How to control drive__delete ↓

What drive__delete does on Proton-MCP

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

Critical Risk

Why drive__delete needs a policy

This tool permanently removes data from Proton Drive and cannot be undone. Deletion of files/folders is an irreversible operation, making it Destructive rather than merely Write. An AI agent misusing this tool could accidentally or maliciously delete user files or entire folder structures, causing significant data loss.

From the tool's definition Tool name is 'drive__delete' with description 'Delete a file or folder from Proton Drive'. The verb 'delete' combined with the action of removing files or folders indicates irreversible data destruction.

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

How to control drive__delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for drive__delete:

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

drive__delete 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 Proton-MCP — 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 drive__delete

What does the drive__delete tool do? +

Delete a file or folder from Proton Drive. It is categorised as a Destructive tool in the Proton-MCP 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 drive__delete? +

Register the Proton- MCP server in PolicyLayer and add a rule for drive__delete: 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 Proton-MCP. Nothing to install.

What risk level is drive__delete? +

drive__delete 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 drive__delete? +

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

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

drive__delete is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proton-MCP tool call.

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

36 Proton-MCP 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.