obsidian_delete_file

THE RISK

Critical Risk

Why obsidian_delete_file needs a policy

The tool deletes files or directories irreversibly. This is a destructive operation that cannot be undone—once deleted, the data is lost unless recovered from backups. The potential blast radius is high because an AI agent could delete critical notes, research, or entire directory structures from a user's vault. It does not involve financial transactions, so it is not Financial.

From the tool's definition Tool name: 'obsidian_delete_file'. Tool description: 'Delete a file or directory from your vault'. The verb 'delete' is explicitly irreversible.

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

POLICY

How to control obsidian_delete_file

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

policy.json

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

obsidian_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 Advanced Obsidian MCP Server — 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 Advanced Obsidian MCP Server tools

Execute obsidian_execute_commands Execute one or more commands in obsidian interface Execute obsidian_open_files Open one or more files in the vault in a new leaf Write obsidian_append_to_file Append content to a new or existing file in the vault Write obsidian_patch_file Insert content into an existing note relative to a heading, block reference, or frontmatte Write obsidian_put_file Create a new file in your vault or update the content of an existing one Read obsidian_batch_get_files Return the contents and metadata of one or more notes (.md files) in your vault Read obsidian_complex_search Complex search for documents using a JsonLogic query with support for 'glob' and 'regexp' Read obsidian_get_active_note Get the content and metadata of the currently active note in Obsidian

All 16 Advanced Obsidian MCP Server 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 Advanced Obsidian MCP Server → 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 obsidian_delete_file

What does the obsidian_delete_file tool do? +

Delete a file or directory from your vault. It is categorised as a Destructive tool in the Advanced Obsidian 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 obsidian_delete_file? +

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

What risk level is obsidian_delete_file? +

obsidian_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 obsidian_delete_file? +

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

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

obsidian_delete_file is provided by the Advanced Obsidian MCP Server MCP server (tokidoo/mcp-obsidian-advanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Advanced Obsidian MCP Server tool call.

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

CHECK YOUR STACK →