delete_files

THE RISK

Critical Risk

Why delete_files needs a policy

This tool irreversibly deletes files and directories, which cannot be undone. Even though deletion may be 'secure' (e.g., with wiping), the action is permanently destructive. An AI agent with misuse could delete critical user files, configurations, or application data. This is the most severe category applicable and justifies 'high' severity given typical desktop filesystem scope.

From the tool's definition Tool name 'delete_files' and description 'Delete single or multiple files and directories securely' explicitly indicate irreversible deletion of data.

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

POLICY

How to control delete_files

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_files"
  ]
}

delete_files disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Vulcan File Ops — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Vulcan File Ops tools

Write file_operations Perform bulk file operations (move, copy, rename) on single or multiple files and director Write edit_file Apply precise modifications to text and code files with intelligent matching.\n\n Write make_directory Create single or multiple directories with recursive parent creation Write move_file Relocate or rename files and directories in a single atomic operation. Write register_directory Register a directory for access. This allows the AI to dynamically gain access Write write_multiple_files Write multiple files concurrently. Supports text, PDF, and DOCX with HTML formatting. Read get_file_info Extract comprehensive metadata and statistics for files or directories. Read glob_files Perform recursive pattern-based searches for files and directories.

All 15 Vulcan File Ops tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Vulcan File Ops → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_files

What does the delete_files tool do? +

Delete single or multiple files and directories securely. It is categorised as a Destructive tool in the Vulcan File Ops 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_files? +

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

What risk level is delete_files? +

delete_files 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_files? +

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

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

delete_files is provided by the Vulcan File Ops MCP server (n0zer0d4y/vulcan-file-ops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vulcan File Ops tool call.

Start from Vulcan File Ops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →