A spanning tree is a graph such that there is exactly one path between any two nodes in the set. A graph can have many possible spanning tree subsets depending on the set of nodes/relationships selected.
AI agents use prize_collecting_steiner_tree to create or update resources in Neo4j Gds — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neo4j Gds environment.
An AI agent can call prize_collecting_steiner_tree faster than any human can review — one bad instruction and it creates or modifies resources in Neo4j Gds by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
A spanning tree is a graph such that there is exactly one path between any two nodes in the set. A graph can have many possible spanning tree subsets depending on the set of nodes/relationships selected. It is categorised as a Write tool in the Neo4j Gds MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neo4j Gds MCP server in PolicyLayer and add a rule for prize_collecting_steiner_tree: 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.
prize_collecting_steiner_tree is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the prize_collecting_steiner_tree 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 prize_collecting_steiner_tree. 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.
prize_collecting_steiner_tree 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 →