delete_item

THE RISK

Critical Risk

Why delete_item needs a policy

Deletion of files or directories from an Obsidian vault cannot be undone through normal tool operations and results in permanent data loss. This is classified as Destructive rather than Write because the action is irreversible. Severity is high because an AI agent invoking this tool without proper safeguards could permanently erase user notes, vault structure, or critical documentation.

From the tool's definition Tool name is 'delete_item' and description explicitly states 'Delete a file or directory from the vault'. The verb 'delete' combined with the capability to remove files or directories represents an irreversible operation.

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

POLICY

How to control delete_item

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

policy.json

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

delete_item 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 Local REST API 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 Obsidian Local REST API MCP Server tools

Write create_or_update_note Create or update a note with content and frontmatter. Performs upsert operation - creates Write write_file Write file content with different modes: overwrite (default), append, or prepend. Handles Read find_related_notes Find notes related to a given note based on shared tags, links, or backlinks Read get_daily_note Get daily note for a specific date. Handles common daily note naming conventions and file Read get_metadata_keys Get all available frontmatter keys from notes Read get_metadata_values Get all unique values for a specific frontmatter key Read get_note Get a specific note with its content and metadata (legacy) Read get_recent_notes Get recently modified notes, ordered by modification time

All 13 Obsidian Local REST API 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 Obsidian Local REST API 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 delete_item

What does the delete_item tool do? +

Delete a file or directory from the vault. It is categorised as a Destructive tool in the Obsidian Local REST API 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 delete_item? +

Register the Obsidian Local REST API MCP Server MCP server in PolicyLayer and add a rule for delete_item: 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 Local REST API MCP Server. Nothing to install.

What risk level is delete_item? +

delete_item 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_item? +

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

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

delete_item is provided by the Obsidian Local REST API MCP Server MCP server (j-shelfwood/obsidian-local-rest-api-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 Local REST API MCP Server tool call.

Start from Obsidian Local REST API 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 →