AI agents call list_sessions 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.
The tool appears to retrieve session metadata without modifying, executing operations, or deleting data. Empty description reduces confidence slightly, but the 'list_' prefix strongly suggests a read-only enumeration. The blast radius of listing sessions is minimal—an attacker could learn about active sessions but cannot directly manipulate them or cause harm through this tool alone.
From the tool's definition Tool name 'list_sessions' indicates a query/retrieval operation that lists existing sessions, consistent with Read operations (list, get, fetch).
Attacks that exploit this kind of access
list_sessions. 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 list_sessions: 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.
list_sessions 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 list_sessions 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 list_sessions. 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.
list_sessions 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 →