Obsidianノートの内容を更新します
AI agents use update_note to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
This tool creates or modifies data reversibly within an Obsidian vault. Users can update note content and later revert changes through Obsidian's version history or undo functionality. It is categorized as Write rather than Destructive because updates are reversible and do not permanently erase data.
From the tool's definition Tool name 'update_note' combined with description 'Obsidianノートの内容を更新します' (updates the content of Obsidian notes) indicates data modification. The Japanese description explicitly states 'update' (更新), confirming this modifies existing note content.
Attacks that exploit this kind of access
Obsidianノートの内容を更新します. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian 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 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 MCP Server MCP server (libra850/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 →