AI agents call delete-note to permanently remove resources in Obsidian MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes user data (notes in an Obsidian vault) and cannot be reversed through the MCP interface. Deletion is irreversible data destruction, placing it in the Destructive category. Severity is high because an AI agent with access to this tool could permanently lose important notes, potentially including sensitive or irreplaceable information.
From the tool's definition Tool name is 'delete-note' with description 'Delete a note'. The server provides 'direct file system access to Obsidian vault files', and this tool irreversibly removes notes from the vault without ability to undo via the API.
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 Server, 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. It is categorised as a Destructive tool in the Obsidian MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian MCP Server 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 Server. 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 MCP server (piotr1215/mcp-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, 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.
9 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.