Create or overwrite a note in the vault.
AI agents use write_note to create or update resources in Mcp Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Obsidian environment.
This tool creates new notes or overwrites existing ones, which is a write operation. It is not destructive because overwrites can be undone (Obsidian maintains history/backups), and the action is reversible through subsequent writes. The severity is medium because an AI agent could overwrite important notes, but the effect is limited to a single vault and is recoverable.
From the tool's definition The tool name is 'write_note' and description states it can 'Create or overwrite a note in the vault.' This is reversible modification of data.
Attacks that exploit this kind of access
Create or overwrite a note in the vault. It is categorised as a Write tool in the Mcp Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Obsidian 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 Mcp Obsidian. 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 Mcp Obsidian MCP server (jkang8/mcp-obsidian). 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 →