get_backlinks
AI agents call get_backlinks to retrieve information from Obsidian MCP (pgvector + Ollama, self-hosted) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves backlink data from the Obsidian vault without modifying state. Despite the empty description, the name and pattern of sibling tools strongly indicate a query operation that returns references to notes linking to a target note. No creation, modification, deletion, or external effects are implied. Classified as Read with high confidence based on naming convention and server context.
From the tool's definition Tool name is 'get_backlinks' which retrieves backlink references; sibling tools include read-only operations like 'get_links', 'get_tags', 'get_recent', 'get_vault_guide', and 'get_neighborhood' that query vault structure without modification.
Attacks that exploit this kind of access
get_backlinks. It is categorised as a Read tool in the Obsidian MCP (pgvector + Ollama, self-hosted) MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server in PolicyLayer and add a rule for get_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 Obsidian MCP (pgvector + Ollama, self-hosted). Nothing to install.
get_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 get_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 get_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.
get_backlinks is provided by the Obsidian MCP (pgvector + Ollama, self-hosted) MCP server (maxkuminov/obsidian-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 →