List all Claude Code sessions with health status. Shows session ID, project, size, message count, and whether the session is healthy, corrupted, empty, or orphaned.
AI agents call list_sessions to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays session information for observability purposes without side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'.
From the tool's definition Tool description states it 'List[s] all Claude Code sessions' and 'Shows session ID, project, size, message count, and whether the session is healthy'.
Documented attack patterns abuse exactly the kind of access list_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for list_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_sessions": {}
}
} list_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Claude Code sessions with health status. Shows session ID, project, size, message count, and whether the session is healthy, corrupted, empty, or orphaned. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for list_sessions: 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 Claude Code Toolkit. Nothing to install.
list_sessions 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 list_sessions 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 list_sessions. 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.
list_sessions is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.