AI agents use upsert_note to create or update resources in Obsidian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian environment.
This tool performs create-or-update operations (upsert) on notes. While not destructive in the sense of irreversible deletion, it can overwrite existing note content entirely, which is a significant modification with potential data loss if the old content is not recoverable through version control. This is a reversible Write operation since notes can typically be restored from backups or version history in Obsidian.
From the tool's definition The tool description states 'Create a note if missing, replace it if it exists. Body is always fully replaced.' This indicates the tool modifies existing notes by replacing their content entirely.
Attacks that exploit this kind of access
Create a note if missing, replace it if it exists. Body is always fully replaced. Frontmatter is replaced by default; pass. It is categorised as a Write tool in the Obsidian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP server in PolicyLayer and add a rule for upsert_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. Nothing to install.
upsert_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 upsert_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 upsert_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.
upsert_note is provided by the Obsidian MCP server (yanxue06/obsidian-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 →