List all active Claude-Code sessions with their status.
AI agents call list_sessions to retrieve information from Claude Code MCP Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this is fundamentally a Read operation with no data modification, the severity is elevated to medium rather than low because the tool exposes information about active Claude Code sessions (which may contain sensitive context about ongoing code execution, prompts, or user activity).
From the tool's definition Tool description states 'List all active Claude-Code sessions with their status' — a retrieval operation with no modification or side effects. The verb 'List' and the read-only nature of querying session status confirm this is a Read operation.
Attacks that exploit this kind of access
List all active Claude-Code sessions with their status. It is categorised as a Read tool in the Claude Code MCP Controller MCP Server, which means it retrieves data without modifying state.
Register the Claude Code MCP Controller 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 MCP Controller. 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 MCP Controller MCP server (mostafa-drz/claude-code-mcp-controller). 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 →