AI agents invoke HDBSCAN to trigger actions in Neo4j Gds. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs a graph clustering algorithm on the database. It is an Execute-category tool because it triggers an external computation/operation (graph algorithm execution) on the Neo4j database. It does not merely read static data — it performs a computational operation whose results depend on graph data and parameters.
From the tool's definition 'Perform HDBSCAN clustering on the graph' — executes a complex graph algorithm (Hierarchical Density-Based Spatial Clustering) on a Neo4j database
Attacks that exploit this kind of access
Perform HDBSCAN clustering on the graph. HDBSCAN, which stands for Hierarchical Density-Based Spatial Clustering of Applications with Noise,. It is categorised as a Execute tool in the Neo4j Gds MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Neo4j Gds MCP server in PolicyLayer and add a rule for HDBSCAN: 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.
HDBSCAN is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the HDBSCAN 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 HDBSCAN. 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.
HDBSCAN 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 →