Update/replace the entire content of an existing note
AI agents use update_note 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.
This tool modifies data reversibly by updating note content rather than destructively removing it. While it can overwrite existing content, the action is not permanent (Obsidian supports undo/version history), distinguishing it from Destructive category.
From the tool's definition Tool description explicitly states 'Update/replace the entire content of an existing note'. The operation modifies existing data (the note content) but is reversible—users can undo changes or restore previous versions through version control or backups.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Update/replace the entire content of an existing 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 update_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 Tools MCP Server. Nothing to install.
update_note 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 update_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 update_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.
update_note 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.
update_note is one line of Obsidian Tools MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →