Search-and-replace within a single note. Supports literal strings or regex patterns. With
AI agents use replace_in_note to create or update resources in Obsidian Mcp Pro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Mcp Pro environment.
This tool creates or modifies data reversibly by replacing content within a note. It does not delete notes (which would be Destructive) or irreversibly remove data, but rather updates existing content. The modification is reversible through undo or re-editing.
From the tool's definition Tool name 'replace_in_note' and description explicitly states 'Search-and-replace' functionality, which modifies note content. The mention of 'regex patterns' indicates pattern-based matching for replacements.
Documented attack patterns abuse exactly the kind of access replace_in_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for replace_in_note:
{
"version": "1",
"default": "deny",
"tools": {
"replace_in_note": {
"limits": [
{
"counter": "replace_in_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} replace_in_note stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search-and-replace within a single note. Supports literal strings or regex patterns. With. It is categorised as a Write tool in the Obsidian Mcp Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Mcp Pro MCP server in PolicyLayer and add a rule for replace_in_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 Pro. Nothing to install.
replace_in_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_in_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_in_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_in_note is provided by the Obsidian Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.