Delete a note or directory from the vault. IMPORTANT: dry_run defaults to true for safety - set dry_run: false to actually delete. Features: - Single note deletion with backlink handling - Directory deletion (requires confirm: true) - Protected paths (.palace/, .obsidian/) cannot be deleted - Bac...
AI agents call palace_delete to permanently remove resources in Obsidian Palace MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (notes or directories) from the user's Obsidian vault. The description explicitly frames deletion as the core action and acknowledges the need for a safety default (dry_run: true), which is strong evidence that the actual operation (dry_run: false) causes permanent data loss that cannot be undone. This is a classic destructive action.
From the tool's definition Delete a note or directory from the vault. IMPORTANT: dry_run defaults to true for safety - set dry_run: false to actually delete.
Attacks that exploit this kind of access
Delete a note or directory from the vault. IMPORTANT: dry_run defaults to true for safety - set dry_run: false to actually delete. Features: - Single note deletion with backlink handling - Directory deletion (requires confirm: true) - Protected paths (.palace/, .obsidian/) cannot be deleted - Backlink options:. It is categorised as a Destructive tool in the Obsidian Palace MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_delete: 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 Palace MCP. Nothing to install.
palace_delete 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 palace_delete 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 palace_delete. 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.
palace_delete is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-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 →