MCP Tool: Deletes a note file, optionally creating a backup first.
AI agents call delete_note to permanently remove resources in Obsidian MCP Tool Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes note files from the Obsidian vault. Even though it offers an optional backup feature, the primary action is irreversible deletion of user data. An AI agent with access to this tool could inadvertently or maliciously destroy important notes. The high severity reflects the potential for significant data loss across the user's knowledge base.
From the tool's definition Tool name is 'delete_note' and description states 'Deletes a note file'. The irreversible deletion of data files is the defining characteristic of the Destructive category.
Documented attack patterns abuse exactly the kind of access delete_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Tool Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_note:
{
"version": "1",
"default": "deny",
"hide": [
"delete_note"
]
}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.
Free to start. No card required.
MCP Tool: Deletes a note file, optionally creating a backup first. It is categorised as a Destructive tool in the Obsidian MCP Tool Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian MCP Tool Server MCP server in PolicyLayer and add a rule for 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 Obsidian MCP Tool Server. Nothing to install.
delete_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
delete_note is provided by the Obsidian MCP Tool Server MCP server (rwb3n/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Obsidian MCP Tool Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Obsidian MCP Tool Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.