delete_file

THE RISK

Critical Risk

Why delete_file needs a policy

This tool irreversibly deletes files when permanent=true is set, which cannot be recovered. Even the default trash behavior is a destructive operation that removes files from normal access. An AI agent with access to this tool could maliciously or accidentally delete critical notes or entire note libraries. The permanent deletion variant makes this clearly Destructive rather than Write, as it is not reversible.

From the tool's definition Tool name is 'delete_file' and description states it 'Delete a file' with option to set 'permanent=true for irreversible deletion'. Even with default soft-delete to trash, the permanent flag enables data that 'cannot be undone' per Destructive definition.

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

POLICY

How to control delete_file

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

policy.json

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

delete_file 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 Obsidian HTTP MCP — 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 Obsidian HTTP MCP tools

Destructive delete_folder Delete all files in a folder recursively. By default moves to .trash-http-mcp/ (soft delet Write create_directory Create a new directory. Idempotent (returns success even if already exists). Does NOT crea Write edit_file Surgically edit file content using exact string replacement (pattern matching). Use this f Write move_file Move or rename a file. Works for both moving to different folder and renaming in same fold Write write_file Create or update a file. Use mode=create for new files, mode=overwrite to replace existing Read find_files Search files in vault with fuzzy matching. Use this when you don\ Read get_file_info Get file metadata (size, modification date). Returns exists: false if file not found. Read list_dir List subdirectories in a path. Returns only folder names (not files). IMPORTANT: Path must

All 12 Obsidian HTTP MCP 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 Obsidian HTTP MCP → 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_file

What does the delete_file tool do? +

Delete a file. By default moves to .trash-http-mcp/ for recovery. Set permanent=true for irreversible deletion. It is categorised as a Destructive tool in the Obsidian HTTP 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 delete_file? +

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

What risk level is delete_file? +

delete_file 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_file? +

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

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

delete_file is provided by the Obsidian HTTP MCP server (nasandnora/obsidian-http-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian HTTP MCP tool call.

Start from Obsidian HTTP MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →