Write or overwrite a note. REQUIRES APPROVAL.
AI agents use write_note to create or update resources in Obsidian MCP Server Plugin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server Plugin environment.
This tool creates or modifies note data reversibly within an Obsidian vault. While it can overwrite existing notes (destructive in appearance), the presence of 'REQUIRES APPROVAL' and the reversible nature of writing files to a local vault classifies it as Write rather than Destructive.
From the tool's definition Tool description explicitly states 'Write or overwrite a note' and requires approval, indicating modification capability. Sibling tools include append_note and search_notes, confirming this tool's write functionality.
Attacks that exploit this kind of access
Write or overwrite a note. REQUIRES APPROVAL. It is categorised as a Write tool in the Obsidian MCP Server Plugin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server Plugin MCP server in PolicyLayer and add a rule for write_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 Plugin. Nothing to install.
write_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 write_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 write_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.
write_note is provided by the Obsidian MCP Server Plugin MCP server (lee3604/obsidian-local-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 →