Moves a note to the system trash. Set
AI agents call obsidian_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 removes data (a note) from the user's vault. Even though items in system trash may theoretically be recoverable at the OS level, from the application's perspective this is a destructive action that cannot be undone through Obsidian's normal undo mechanisms. An AI agent with access to this tool could accidentally or maliciously delete important notes, causing data loss.
From the tool's definition The tool description states 'Moves a note to the system trash' - this is an irreversible deletion operation. Once moved to trash, the note data is removed from the Obsidian vault and cannot be undone through normal application operations.
Attacks that exploit this kind of access
Moves a note to the system trash. Set. 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 obsidian_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.
obsidian_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 obsidian_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 obsidian_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.
obsidian_delete_note is provided by the Obsidian MCP server (yuchi-chang/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 →