Delete a note from the Obsidian vault
AI agents call delete_note to permanently remove resources in Enhanced Obsidian MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes notes from a knowledge base without reversal capability. While the blast radius is somewhat limited to a single vault rather than external systems, the irreversible nature of deletion and potential loss of important knowledge base content justifies the Destructive category and high severity. Confidence is high due to explicit use of 'delete' verb and unambiguous destructive semantics.
From the tool's definition Tool name 'delete_note' combined with description 'Delete a note from the Obsidian vault' explicitly performs irreversible deletion of data.
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 Enhanced Obsidian MCP 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.
Delete a note from the Obsidian vault. It is categorised as a Destructive tool in the Enhanced Obsidian MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enhanced Obsidian MCP 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 Enhanced Obsidian MCP 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 Enhanced Obsidian MCP Server MCP server (jianruidutong/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Enhanced Obsidian MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Enhanced Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.