Delete a note from the vault. Destructive — only call when the user has explicitly asked to remove a file.
AI agents call delete_note to permanently remove resources in Obsidian — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a note/file from an Obsidian vault). Deletion cannot be undone through normal tool operations, making it Destructive rather than merely Write. The blast radius is high because an AI agent could accidentally delete important user notes if confused about intent or given ambiguous instructions.
From the tool's definition Tool name is 'delete_note' and description explicitly states 'Delete a note from the vault. Destructive — only call when the user has explicitly asked to remove a file.'
Attacks that exploit this kind of access
Delete a note from the vault. Destructive — only call when the user has explicitly asked to remove a file. It is categorised as a Destructive tool in the Obsidian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian 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. 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 server (yanxue06/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →