Get unified snapshot of current session state including todos, git status, context files, and session info.
AI agents call get_session_state to retrieve information from Claude Session MCP 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 metadata (todos, git status, context files, session info) without creating, modifying, deleting, or executing operations. It has no side effects on the system or data. It is purely informational, fitting the Read category.
From the tool's definition Tool description states it 'Get[s] unified snapshot of current session state' — a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Get unified snapshot of current session state including todos, git status, context files, and session info. It is categorised as a Read tool in the Claude Session MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Session MCP server in PolicyLayer and add a rule for get_session_state: 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 Session MCP. Nothing to install.
get_session_state 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_state 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_state. 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_state is provided by the Claude Session MCP server (timevans/ccsession). 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 →