client_cleanup_status
Review client-owned effects and whether the session can finish cleanly. This check does not stop anything.
tool · Connected client
Before you start
Use the same client that ran the test, before logging out. This checks its outstanding effects, not another developer’s session.
Access: Your MCP client needs the serverResource capability for this tool.
Request
{
"name": "client_cleanup_status",
"arguments": {}
}No arguments are needed for this example.
Illustrative tools/call parameters. Inspect the tool’s inputSchema in tools/list before sending them.
What to look for
Review client-owned effects and whether the session can finish cleanly. This check does not stop anything.
If the result is unexpected
Do not infer cleanup from a quiet capture. Resolve reported outstanding state on the Mac.
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 cleanup status.
Browse all MCP reference entries →