obsidian_delete_note

THE RISK

Critical Risk

Why obsidian_delete_note needs a policy

This tool permanently removes data (notes) without possibility of recovery through normal means. It is categorized as Destructive rather than Execute because the primary function is irreversible data deletion, not conditional code execution. The 'expectedHash or expectedMtime' guards provide some safety against accidental misuse, but do not change the destructive nature of the operation.

From the tool's definition Tool performs 'headless-guarded filesystem delete for explicit filePath targets' - this irreversibly removes note files from the Obsidian vault. The tool name explicitly contains 'delete' and the description confirms it deletes files.

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

POLICY

How to control obsidian_delete_note

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

policy.json

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

obsidian_delete_note 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 Optimike Obsidian 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 Optimike Obsidian MCP tools

Destructive obsidian_admin_filesystem Headless-filesystem admin batch operations with dry-run by default. Supports sandbox-safe Execute obsidian_search_replace Headless-guarded filesystem exact search/replace for filePath targets. Execute obsidian_runtime_maintenance Runs integrity checks, maintenance, or cache refresh actions for the local shared runtime. Write obsidian_batch_frontmatter Headless-filesystem batch frontmatter set with dry-run support. Protected keys remain bloc Write bases_create Headless-guarded filesystem .base create/validate. Writes YAML directly and does not evalu Write bases_upsert_config Headless-guarded filesystem .base config replacement/validation. Write bases_upsert_rows Headless-guarded filesystem frontmatter set operations for notes referenced by a .base. Un Write obsidian_manage_canvas Headless filesystem JSON Canvas helper. Validates, creates, adds text nodes, and connects

All 15 Optimike Obsidian 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 Optimike Obsidian 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 obsidian_delete_note

What does the obsidian_delete_note tool do? +

Headless-guarded filesystem delete for explicit filePath targets. Requires expectedHash or expectedMtime. It is categorised as a Destructive tool in the Optimike Obsidian 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 obsidian_delete_note? +

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

What risk level is obsidian_delete_note? +

obsidian_delete_note 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_note? +

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

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

obsidian_delete_note is provided by the Optimike Obsidian MCP server (optimikelabs/optimike-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Optimike Obsidian MCP tool call.

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

CHECK YOUR STACK →