replace_obsidian_note
AI agents use replace_obsidian_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.
The tool replaces (modifies) note content in Obsidian vaults. This is a Write operation because replacement is reversible—the previous version could theoretically be recovered from Obsidian's version history or undo functionality, distinguishing it from Destructive (which is permanent).
From the tool's definition Tool name is 'replace_obsidian_note' which indicates it modifies existing note content. The sibling tools include 'delete_obsidian_note' (destructive), 'create_obsidian_note' (write), and 'append_to_obsidian_note' (write), establishing this server's pattern…
Attacks that exploit this kind of access
replace_obsidian_note. 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 replace_obsidian_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.
replace_obsidian_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 replace_obsidian_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 replace_obsidian_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.
replace_obsidian_note is provided by the Obsidian MCP Server MCP server (nbaradar/obsidian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
replace_obsidian_note is one line of Obsidian MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →