get_session_summary
Compact recovery session summary with progress, status, and next actions for handoff. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-session-summary.md
What get_session_summary does on Delx MCP Server
AI agents call get_session_summary to retrieve information from Delx MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | The session ID to summarize |
Parameters from the server's own tool schema.
Why get_session_summary is rated Low
This tool queries and returns existing session data (summary, progress tracking, status information) without creating, modifying, deleting, or executing side effects. The mention of 'dynamic pricing' and API references does not change the core function: it retrieves information for handoff purposes.
From the tool's definition Tool retrieves a 'session summary' with 'progress, status, and next actions' — described as a read operation for a recovery workflow. No modification, deletion, or execution of external commands is indicated.
Attacks that exploit this kind of access
The rule that runs get_session_summary 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 get_session_summary, this is the rule to start with:
get_session_summary is read-only, so it stays allowed. 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 get_session_summary call is checked against it from then on.
Questions about get_session_summary
Compact recovery session summary with progress, status, and next actions for handoff. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_session_summary accepts 1 parameter: session_id. Required: session_id. 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 get_session_summary: 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.
get_session_summary 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 get_session_summary 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 get_session_summary. 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.
get_session_summary is provided by the Delx MCP Server MCP server (delx-mcp-server). 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