Insert content under a specific heading in a note
AI agents use insert_at_heading to create or update resources in Obsidian Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Tools MCP Server environment.
The tool creates or modifies data (inserting content into a note) in a reversible manner. It does not execute code, delete data irreversibly, move money, or perform destructive operations. While the sibling tools include 'delete_note' (destructive) and 'create_note' (write), this specific tool is classified as Write because it modifies existing notes by inserting content at a specific location.
From the tool's definition Tool name 'insert_at_heading' and description 'Insert content under a specific heading in a note' indicate modification of existing note content. This is a reversible write operation that adds content to a note without deleting or executing code.
Attacks that exploit this kind of access
Insert content under a specific heading in a note. It is categorised as a Write tool in the Obsidian Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Tools MCP Server MCP server in PolicyLayer and add a rule for insert_at_heading: 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 Tools MCP Server. Nothing to install.
insert_at_heading is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the insert_at_heading 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 insert_at_heading. 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.
insert_at_heading is provided by the Obsidian Tools MCP Server MCP server (sureshsankaran/obsidian-tools-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 →