AI agents call betweenness_centrality 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.
Betweenness centrality is a standard graph metric that calculates node importance by counting shortest paths. Based on context—the server's purpose is to 'answer graph-related questions' and all sibling tools are read-only analytical algorithms—this tool retrieves and computes graph properties without creating, modifying, or deleting data.
From the tool's definition Tool name 'betweenness_centrality' is a graph analysis algorithm; sibling tools like 'article_rank', 'closeness_centrality', 'articulation_points', and 'breadth_first_search' are all read-only graph query/analysis operations that retrieve computed metrics…
Attacks that exploit this kind of access
betweenness_centrality. 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 betweenness_centrality: 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.
betweenness_centrality 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 betweenness_centrality 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 betweenness_centrality. 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.
betweenness_centrality 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 →