Edit a specific section of a note. For headings: targets are created if missing. Tip: use vault_read first to understand the note structure before patching.
AI agents use vault_patch 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 note content reversibly by editing specific sections or creating missing heading targets. It does not delete data irreversibly (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not create financial obligations.
From the tool's definition Tool description states 'Edit a specific section of a note' and 'targets are created if missing', indicating modification of note content. The tool name 'vault_patch' and verb 'Edit' confirm write operations.
Attacks that exploit this kind of access
Edit a specific section of a note. For headings: targets are created if missing. Tip: use vault_read first to understand the note structure before patching. 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_patch: 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_patch 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_patch 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_patch. 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_patch 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 →