Delete a file from the vault (moves to trash by default)
AI agents call delete to permanently remove resources in Obsidian Local — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes files from the Obsidian vault, which is a destructive, irreversible action. Even though files go to trash rather than being permanently purged, the deletion of vault content cannot be undone within the vault's normal workflow and constitutes data loss. If an AI agent misuses this tool, it could delete important notes without user consent, causing significant data loss.
From the tool's definition Tool name 'delete' combined with description 'Delete a file from the vault (moves to trash by default)' - the verb 'delete' and the action of removing files from a vault are destructive operations.
Attacks that exploit this kind of access
Delete a file from the vault (moves to trash by default). It is categorised as a Destructive tool in the Obsidian Local MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian Local MCP server in PolicyLayer and add a rule for 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 Local. Nothing to install.
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 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 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.
delete is provided by the Obsidian Local MCP server (matthewsuazo/obsidian-local-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 →