Get detailed status information for a specific session.
AI agents call get_session_status 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.
This tool retrieves and queries session status information without modifying, executing, or deleting any data. It is a read-only operation that returns information about an existing session. The low severity reflects minimal risk even if accessed by unauthorized agents, as it only exposes monitoring/status data.
From the tool's definition Tool name 'get_session_status' and description 'Get detailed status information for a specific session' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get detailed status information for a specific session. 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 get_session_status: 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.
get_session_status 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 get_session_status 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 get_session_status. 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.
get_session_status 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 →