Delete a note. By default the file is moved to the vault
AI agents call delete_note to permanently remove resources in Obsidian Mcp Pro — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a note from the user's Obsidian vault. Even if moved to trash, it represents permanent deletion of user data that cannot be recovered through normal tool operations. The high severity reflects the potential for an AI agent to inadvertently delete important notes, research, or personal knowledge.
From the tool's definition Tool name is 'delete_note' and description states 'Delete a note'. The description explicitly indicates the note file is 'moved to the vault' (likely meaning trash/recycle), but deletion of notes in a knowledge management system is an irreversible data loss…
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 Pro, 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. By default the file is moved to the vault. It is categorised as a Destructive tool in the Obsidian Mcp Pro MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Mcp Pro 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 Pro. 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 Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, 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.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.