AI agents call bellman_ford_single_source_shortest_path to retrieve information from Neo4j Gds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Bellman-Ford is a read-only graph algorithm that calculates shortest paths. It queries existing graph data and returns results without creating, modifying, or deleting any data. Severity is low as misuse only returns graph topology information.
From the tool's definition 'computes the shortest path between nodes' — pure graph traversal/query with no data modification
Attacks that exploit this kind of access
The Bellman-Ford Path algorithm computes the shortest path between nodes. It is categorised as a Read tool in the Neo4j Gds MCP Server, which means it retrieves data without modifying state.
Register the Neo4j Gds MCP server in PolicyLayer and add a rule for bellman_ford_single_source_shortest_path: 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 Neo4j Gds. Nothing to install.
bellman_ford_single_source_shortest_path 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 bellman_ford_single_source_shortest_path 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 bellman_ford_single_source_shortest_path. 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.
bellman_ford_single_source_shortest_path is provided by the Neo4j Gds MCP server (neo4j-contrib/gds-agent). 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 →