Automatically add backlinks throughout the entire vault by detecting note names in content and converting them to wikilinks
AI agents use auto_backlink_vault to create or update resources in Obsidian MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP environment.
This tool modifies note content by automatically inserting wikilinks into existing notes based on detected note names. While the changes are reversible (notes can be edited to remove added links), the tool operates at scale across the entire vault, making it a Write-category operation.
From the tool's definition The tool description states it will 'automatically add backlinks throughout the entire vault' and 'converting them to wikilinks', which modifies note content across potentially many files. This is a write operation that reversibly updates multiple notes.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access auto_backlink_vault gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for auto_backlink_vault:
{
"version": "1",
"default": "deny",
"tools": {
"auto_backlink_vault": {
"limits": [
{
"counter": "auto_backlink_vault_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}auto_backlink_vault 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.
Automatically add backlinks throughout the entire vault by detecting note names in content and converting them to wikilinks. It is categorised as a Write tool in the Obsidian MCP 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 auto_backlink_vault: 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. Nothing to install.
auto_backlink_vault 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 auto_backlink_vault 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 auto_backlink_vault. 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.
auto_backlink_vault is provided by the Obsidian MCP server (newtype-01/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Obsidian MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Obsidian MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.