breadth_first_search

The Breadth First Search algorithm is a graph traversal algorithm that given a start node visits nodes in order of increasing distance, see https://en.wikipedia.org/wiki/Breadth-first_search.

Server Neo4j Gds neo4j-contrib/gds-agent
Category Read
Risk class Low
Parameters 00 required

What breadth_first_search does on Neo4j Gds

AI agents call breadth_first_search 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.

Why breadth_first_search needs a policy

Breadth-first search is a pure traversal and analysis algorithm that reads graph structure to explore connectivity. It has no side effects on the Neo4j database—it neither creates, modifies, nor deletes data, nor does it execute arbitrary code or trigger external operations. The blast radius of misuse is minimal since it only accesses existing graph data. This clearly falls under the Read category.

From the tool's definition Tool is a graph traversal algorithm that 'visits nodes in order of increasing distance' and does not modify, delete, or execute external operations on the data

Questions about breadth_first_search

What does the breadth_first_search tool do? +

The Breadth First Search algorithm is a graph traversal algorithm that given a start node visits nodes in order of increasing distance, see https://en.wikipedia.org/wiki/Breadth-first_search. It is categorised as a Read tool in the Neo4j Gds MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on breadth_first_search? +

Register the Neo4j Gds MCP server in PolicyLayer and add a rule for breadth_first_search: 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.

What risk level is breadth_first_search? +

breadth_first_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit breadth_first_search? +

Yes. Add a rate_limit block to the breadth_first_search 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.

How do I block breadth_first_search completely? +

Set action: deny in the PolicyLayer policy for breadth_first_search. 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.

What MCP server provides breadth_first_search? +

breadth_first_search 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.