find_related
AI agents call find_related 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.
Despite the empty description, the tool's name and position among other Read-category siblings (which traverse wikilinks and retrieve note relationships) indicate this finds semantically or structurally related notes without modification. No evidence of data mutation, deletion, or external execution.
From the tool's definition Tool named 'find_related' with no description; context shows this is part of a semantic search system (pgvector + Ollama). Sibling tools like 'get_backlinks', 'get_links', 'get_neighborhood', and 'get_recent' are all Read operations.
Attacks that exploit this kind of access
find_related. 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 find_related: 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.
find_related 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 find_related 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 find_related. 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.
find_related 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 →