AI agents call weakly_connected_components 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.
Weakly Connected Components is a graph analysis algorithm that retrieves and computes information about graph connectivity. It does not create, modify, delete, or execute arbitrary code - it performs a deterministic, read-only computation on existing graph data. The severity is low because even if executed against unintended graphs, the impact is limited to retrieving analytical results without side effects.
From the tool's definition Tool description states it 'finds sets of connected nodes' - a pure query operation with no data modification. The algorithm analyzes graph structure without side effects. Named tools on this server (search, list, get operations) reinforce read-only pattern.
Attacks that exploit this kind of access
The Weakly Connected Components (WCC) algorithm finds sets of connected nodes in directed and undirected graphs. 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 weakly_connected_components: 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.
weakly_connected_components 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 weakly_connected_components 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 weakly_connected_components. 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.
weakly_connected_components 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 →