Find notes that reference the given note via [[wikilink]].
AI agents call obsidian_backlinks to retrieve information from Second Brain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves backlink relationships between notes in an Obsidian vault. It does not create, modify, delete, or execute any code. The operation is purely informational—traversing existing references. The low severity reflects that misuse would only expose existing vault structure and relationships, not enable destructive or financial harm.
From the tool's definition Tool description states it finds notes that reference a given note—a query operation with no modification. The server description emphasizes 'read-only semantic search' and 'human-approved write workflow', establishing that this tool performs retrieval only.
Attacks that exploit this kind of access
Find notes that reference the given note via [[wikilink]]. It is categorised as a Read tool in the Second Brain MCP Server, which means it retrieves data without modifying state.
Register the Second Brain MCP server in PolicyLayer and add a rule for obsidian_backlinks: 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 Second Brain. Nothing to install.
obsidian_backlinks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the obsidian_backlinks 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 obsidian_backlinks. 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.
obsidian_backlinks is provided by the Second Brain MCP server (noesskeetit/second-brain-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 →