Traverse the wikilink graph outward from a starting note and return every note reachable within N hops, grouped by depth level with an indented tree visualization. Each neighbor is tagged with its hop distance and direction (inbound = reached via backlink, outbound = reached via outlink). Use to ...
AI agents call get_graph_neighbors to retrieve information from Obsidian Mcp Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_graph_neighbors performs read-only graph traversal to retrieve neighbor notes within N hops. It has no side effects—it queries existing relationships and returns results without creating, modifying, or deleting any data. This is a classic Read category operation with minimal risk.
From the tool's definition Tool traverses and returns wikilink graph data without modifying any notes or structure. Description uses 'return' and 'explore' language indicating query-only operations.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_graph_neighbors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for get_graph_neighbors:
{
"version": "1",
"default": "deny",
"tools": {
"get_graph_neighbors": {}
}
}get_graph_neighbors is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Traverse the wikilink graph outward from a starting note and return every note reachable within N hops, grouped by depth level with an indented tree visualization. Each neighbor is tagged with its hop distance and direction (inbound = reached via backlink, outbound = reached via outlink). Use to explore a topic cluster, map a note. It is categorised as a Read tool in the Obsidian Mcp Pro MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Mcp Pro MCP server in PolicyLayer and add a rule for get_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 Obsidian Mcp Pro. Nothing to install.
get_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 get_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 get_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.
get_graph_neighbors is provided by the Obsidian Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.