Get what has been accomplished this session - completed todos, files modified, tool calls, git commits.
AI agents call get_session_history 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 historical information about completed tasks, modified files, tool calls, and git commits—all read-only query operations. It has no destructive, financial, or execution capability, and does not create or modify data. The blast radius of misuse is minimal, as an AI agent could only gain visibility into session history without affecting system state.
From the tool's definition Tool name 'get_session_history' and description 'Get what has been accomplished this session' indicate retrieval of session data without modification or side effects.
Attacks that exploit this kind of access
Get what has been accomplished this session - completed todos, files modified, tool calls, git commits. 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_history: 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_history 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_history 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_history. 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_history 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 →