Insert new content into a note at a specific position. Does not modify existing content — use replace for that.
AI agents use Insert to create or update resources in Nexus MCP for Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus MCP for Obsidian environment.
The Insert tool creates new content within a note, which is a write operation. It is reversible (the inserted content can be removed or edited later), so it does not qualify as Destructive. The severity is medium because inserting malicious or incorrect content into notes could degrade vault integrity or cause confusion, but the impact is limited to additive changes within the user's local vault.
From the tool's definition Tool description states 'Insert new content into a note at a specific position' — this creates or modifies data reversibly by adding content to an existing note without deletion or destruction.
Attacks that exploit this kind of access
Insert new content into a note at a specific position. Does not modify existing content — use replace for that. It is categorised as a Write tool in the Nexus MCP for Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus MCP for Obsidian MCP server in PolicyLayer and add a rule for Insert: 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 Nexus MCP for Obsidian. Nothing to install.
Insert 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 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. 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 is provided by the Nexus MCP for Obsidian MCP server (profsynapse/nexus). 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 →