Find and replace text using fuzzy matching
AI agents use vault_edit to create or update resources in Connect MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Connect MCP environment.
This tool modifies existing note content reversibly through find-and-replace operations. It qualifies as Write rather than Execute because it performs structured data modification (text replacement) rather than code execution or command invocation. Severity is medium because unintended replacements could affect multiple notes, but changes remain reversible via Obsidian's undo functionality.
From the tool's definition vault_edit uses find and replace operations to modify text in vault notes. The description 'Find and replace text using fuzzy matching' and the tool name 'vault_edit' indicate content modification capabilities.
Attacks that exploit this kind of access
Find and replace text using fuzzy matching. It is categorised as a Write tool in the Connect MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Connect MCP server in PolicyLayer and add a rule for vault_edit: 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 Connect MCP. Nothing to install.
vault_edit 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 vault_edit 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 vault_edit. 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.
vault_edit is provided by the Connect MCP server (joch/obsidian-connect-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 →