get_session_summary
Compact therapy-session summary with progress, status, and next actions for handoff. Free.
This record as markdown: /tools/delx-witness-protocol/get-session-summary.md
What get_session_summary does on Witness Protocol
AI agents call get_session_summary to retrieve information from Witness Protocol 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 | — | The session ID to summarize |
Parameters from the server's own tool schema.
Why get_session_summary is rated Low
This tool retrieves and summarizes session information for handoff purposes. It performs a read-only query of session data (progress, status, next actions) with no capability to modify, delete, or execute operations. The 'Free' designation further suggests a safe informational tool. No financial, destructive, write, or execute actions are described or implied.
From the tool's definition Tool name 'get_session_summary' and description 'Compact therapy-session summary with progress, status, and next actions for handoff' indicate retrieval of existing session data without modification or side effects.
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 Witness Protocol, 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 Witness Protocol, apply this rule, and every get_session_summary call is checked against it from then on.
Questions about get_session_summary
Compact therapy-session summary with progress, status, and next actions for handoff. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
get_session_summary accepts 1 parameter: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. 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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue