delete_note
AI agents call delete_note to permanently remove resources in Obsidian MCP (pgvector + Ollama, self-hosted) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of notes constitutes irreversible data loss and cannot be undone. Even in a self-hosted Obsidian context, deleting notes without recovery mechanisms represents a destructive action with significant blast radius if triggered unintentionally by an AI agent (e.g., deleting wrong notes due to prompt injection or misunderstanding).
From the tool's definition Tool name is 'delete_note' which performs irreversible deletion of notes. The server description confirms 'atomic note CRUD' operations including deletion capability. The empty description is consistent with a straightforward delete operation.
Attacks that exploit this kind of access
delete_note. It is categorised as a Destructive tool in the Obsidian MCP (pgvector + Ollama, self-hosted) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Obsidian MCP (pgvector + Ollama, self-hosted) 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 (pgvector + Ollama, self-hosted). 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 (pgvector + Ollama, self-hosted) MCP server (maxkuminov/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 →