Create a new note or overwrite an existing one
AI agents use write_note to create or update resources in Obsidian Vault MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Vault MCP Server environment.
This tool performs reversible data modification—creating new notes or overwriting existing ones. While it can overwrite data, the operation is not permanently destructive (notes can be recovered via version history, undo, or backups in Obsidian Sync). It does not delete, purge, execute code, or move money.
From the tool's definition Tool description states 'Create a new note or overwrite an existing one'. The name 'write_note' and the capability to create or modify notes clearly indicate write operations.
Attacks that exploit this kind of access
Create a new note or overwrite an existing one. It is categorised as a Write tool in the Obsidian Vault MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Vault MCP Server 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 Vault MCP Server. 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 Vault MCP Server MCP server (jonhollander/obsidian-mcp-cloudflare). 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 →