AI agents use k_nearest_neighbors 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.
The tool explicitly creates new relationships in the graph database as part of its operation. This is a write operation that modifies the graph structure by adding edges, which is reversible (relationships can be deleted) but does persistently alter the database state.
From the tool's definition creates new relationships between each node and its k nearest neighbors
Attacks that exploit this kind of access
The K-Nearest Neighbors algorithm computes a distance value for all node pairs in the graph and creates new relationships between each node and its k nearest neighbors. 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 k_nearest_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 Neo4j Gds. Nothing to install.
k_nearest_neighbors 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 k_nearest_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 k_nearest_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.
k_nearest_neighbors 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 →