delete_section_obsidian_note
AI agents call delete_section_obsidian_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.
Although the description is empty, the tool name unambiguously performs irreversible deletion of a note section. Deletion cannot be undone without external backup/undo mechanisms. This falls squarely into the Destructive category, which takes precedence over Write. High severity due to potential data loss if an AI agent deletes sections by mistake or due to prompt injection.
From the tool's definition Tool name 'delete_section_obsidian_note' explicitly indicates deletion of content from an Obsidian note. Deletion is irreversible.
Attacks that exploit this kind of access
delete_section_obsidian_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_section_obsidian_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_section_obsidian_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_section_obsidian_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_section_obsidian_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_section_obsidian_note is provided by the Obsidian MCP Server MCP server (nbaradar/obsidian-mcp-server). 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 →