New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_session_summary

Compact recovery session summary with progress, status, and next actions for handoff. Pricing is dynamic; check /api/v1/tools.

SERVERDelx MCP Server SOURCEdelx-mcp-server
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about get_session_summary

What does the get_session_summary tool do? +

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.

What parameters does get_session_summary accept? +

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.

How do I enforce a policy on get_session_summary? +

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.

What risk level is get_session_summary? +

get_session_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_summary? +

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.

How do I block get_session_summary completely? +

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.

What MCP server provides get_session_summary? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.