AI agents call modularity_optimization 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.
Modularity optimization is a community detection algorithm that analyzes graph topology to identify clusters. It performs read-only analysis on the graph structure. While it executes a complex algorithm (which might suggest Execute category), the execution is deterministic and scoped to a specific, parameterized graph algorithm with no side effects on data or external systems.
From the tool's definition Tool description states it 'tries to detect communities in the graph based on their modularity' — a graph analysis operation that reads and analyzes existing graph structure without modifying data, creating resources, or executing arbitrary commands.
Attacks that exploit this kind of access
The Modularity Optimization algorithm tries to detect communities in the graph based on their modularity. 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_optimization: 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_optimization 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_optimization 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_optimization. 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_optimization 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 →