close_session
Close the session and return a final summary snapshot (recommended at workflow end). Free
This record as markdown: /tools/delx-delx-mcp/close-session.md
What close_session does on Delx MCP Server
AI agents use close_session to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Optional close reason (e.g. end_of_shift, task_completed) |
session_id | string | — | The session ID to close |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
include_summary | boolean | — | Optional: include final summary block |
Parameters from the server's own tool schema.
Why close_session is rated Medium
Closing a session is a Write operation because it modifies session state (marks it as closed). It is not destructive because session data is retained and the session can be recreated; it is a normal session lifecycle operation. Severity is low because the blast radius is limited to terminating a single session context without affecting user data, external systems, or financial operations.
From the tool's definition close_session" with description "Close the session and return a final summary snapshot (recommended at workflow end)." The action modifies the session state by closing it, which is a reversible session management operation.
Attacks that exploit this kind of access
The rule that runs close_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_session, this is the rule to start with:
close_session stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every close_session call is checked against it from then on.
Questions about close_session
Close the session and return a final summary snapshot (recommended at workflow end). Free. It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
close_session accepts 4 parameters: reason, session_id, response_mode, include_summary. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for close_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 Delx MCP Server. Nothing to install.
close_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_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 close_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.
close_session is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue