AI agents call local_clustering_coefficient 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.
Local clustering coefficient is a standard graph analytics computation that retrieves and analyzes existing graph structure to produce insights. It performs no writes, deletions, executions of external code, or financial transactions. The computation is deterministic and based solely on the graph's existing topology. This is a classic Read operation — querying and analyzing data with no side effects.
From the tool's definition The tool 'computes the local clustering coefficient for each node in the graph' — a purely analytical operation that measures graph properties without modifying data, triggering external operations, or moving money.
Attacks that exploit this kind of access
The Local Clustering Coefficient algorithm computes the local clustering coefficient for each node in the graph. 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 local_clustering_coefficient: 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.
local_clustering_coefficient 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 local_clustering_coefficient 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 local_clustering_coefficient. 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.
local_clustering_coefficient 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 →