Get neighboring notes in the graph up to specified depth.
AI agents call graph_neighbors to retrieve information from Graph Rag Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns neighboring note relationships from the graph structure. The verb 'Get' combined with the read-only nature of traversing graph relationships (no side effects, no data modification, no code execution) clearly categorizes this as a Read operation. The blast radius is minimal since it only surfaces existing graph metadata to the user.
From the tool's definition Tool name 'graph_neighbors' and description 'Get neighboring notes in the graph up to specified depth' indicate a retrieval operation that queries graph structure without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get neighboring notes in the graph up to specified depth. It is categorised as a Read tool in the Graph Rag Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for graph_neighbors: 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 Graph Rag Obsidian. Nothing to install.
graph_neighbors 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 graph_neighbors 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 graph_neighbors. 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.
graph_neighbors is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). 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 →