delete_session
AI agents call delete_session to permanently remove resources in Neo4j Gds — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Delete operations are irreversible and destructive by definition. While the exact scope is unclear due to empty description, deleting a session could terminate active computations, clear cached results, or remove user state in ways that cannot be undone. High severity due to potential loss of work or data.
From the tool's definition Tool named 'delete_session' with no description provided. The verb 'delete' combined with 'session' indicates irreversible removal of session state or data.
Attacks that exploit this kind of access
delete_session. It is categorised as a Destructive tool in the Neo4j Gds MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Neo4j Gds MCP server in PolicyLayer and add a rule for delete_session: 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.
delete_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_session 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 delete_session. 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.
delete_session 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 →