List all managed sessions (metadata) plus any live tmux sessions.
AI agents call session_list to retrieve information from Claude Code without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward query/retrieval of session metadata and tmux state. It has no side effects, does not execute code, does not modify data, and does not delete or destroy resources. The blast radius of misuse is minimal—an agent could learn about existing sessions but cannot act upon them without using other tools like session_start, session_send, or session_destroy.
From the tool's definition Tool name is 'session_list' and description states it will 'List all managed sessions (metadata) plus any live tmux sessions.' The verb 'list' is a read-only operation that retrieves and returns information without modifying state.
Attacks that exploit this kind of access
List all managed sessions (metadata) plus any live tmux sessions. It is categorised as a Read tool in the Claude Code MCP Server, which means it retrieves data without modifying state.
Register the Claude Code MCP server in PolicyLayer and add a rule for session_list: 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. Nothing to install.
session_list 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 session_list 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 session_list. 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.
session_list is provided by the Claude Code MCP server (joschi655/claude-code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →