file_delete

Permanently delete one file an app has stored.

SERVEROpen Mcp Apps SOURCE@2nd1st/open-mcp-apps

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/2nd1st-open-mcp-apps/file-delete.md

WHAT IT DOES

What file_delete does on Open Mcp Apps

AI agents call file_delete to permanently remove resources in Open Mcp Apps, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why file_delete is rated Critical

This tool destroys data irreversibly by permanently deleting files. Even though it operates on a single file (limiting blast radius compared to bulk deletion), the permanent nature and inability to recover the deleted file places it in the Destructive category, which ranks higher than Write, Execute, or Read.

From the tool's definition Tool name is 'file_delete' with description 'Permanently delete one file an app has stored.' The use of 'Permanently delete' indicates an irreversible action that cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs file_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Open Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_delete, this is the rule to start with:

file_delete Hidden

file_delete 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": [
    "file_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about file_delete

What does the file_delete tool do? +

Permanently delete one file an app has stored. It is categorised as a Destructive tool in the Open Mcp Apps 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 file_delete? +

Register the Open Mcp Apps MCP server in PolicyLayer and add a rule for file_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 Open Mcp Apps. Nothing to install.

What risk level is file_delete? +

file_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 file_delete? +

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

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

file_delete is provided by the Open Mcp Apps MCP server (@2nd1st/open-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Open Mcp Apps, and thousands of servers like it.

This server

All 32 Open Mcp Apps tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →