session_summary

tool · Connected client

Before you start

Copy a session ID from list or search. Start with the metadata-only example. Asking for headers, query values, or a body introduces separate headerRead, queryRead, or bodyRead checks.

Access: Your MCP client needs the sessionSummary capability for this tool.

Request

{
  "name": "session_summary",
  "arguments": {
    "sessionID": "11111111-1111-4111-8111-111111111111"
  }
}

sessionID

Use the identifier of a retained test request, not the HTTP URL or a row number.

Illustrative tools/call parameters. Inspect the tool’s inputSchema in tools/list before sending them. Replace the synthetic UUID with the identifier from your own authorized session.

What to look for

Inspect one captured request rather than exporting the whole session list.

If the result is unexpected

Replace the example UUID with a current session ID. A summary may legitimately omit a body.

What to check if access is denied

Effects and cleanup

This request reads information; it does not start a test or activate a traffic change. Treat returned metadata and any exported evidence as potentially sensitive.

Same underlying tool: joesproxyctl session show.

Browse all MCP reference entries →