AI agents call modularity_metric 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.
This tool retrieves or calculates a metric to evaluate graph analysis results without modifying, executing external operations, deleting data, or committing financial actions. It is a pure query/analysis operation on already-detected communities, consistent with other graph algorithm tools on this server that report metrics or properties rather than perform destructive operations.
From the tool's definition Tool name 'modularity_metric' and description 'Modularity is a metric that allows you to evaluate the quality of a community detection' indicate a read-only analytical operation that computes and returns a quality metric for existing community detection…
Attacks that exploit this kind of access
Modularity is a metric that allows you to evaluate the quality of a community detection. 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 modularity_metric: 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.
modularity_metric 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 modularity_metric 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 modularity_metric. 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.
modularity_metric 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 →