Get intelligent recommendation on whether to reset context. Analyzes context usage, todo completion, git state, and session duration.
AI agents call should_reset_context 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.
The tool reads and analyzes existing state (context usage, todos, git state, session duration) to produce a recommendation. It does not modify any data, execute commands, or trigger side effects — it only retrieves and evaluates information to suggest an action.
From the tool's definition 'Get intelligent recommendation on whether to reset context. Analyzes context usage, todo completion, git state, and session duration.'
Attacks that exploit this kind of access
Get intelligent recommendation on whether to reset context. Analyzes context usage, todo completion, git state, and session duration. 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 should_reset_context: 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.
should_reset_context 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 should_reset_context 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 should_reset_context. 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.
should_reset_context 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 →