Get recent session checkpoints. Returns a chronological list of what the developer worked on.
AI agents call get_session_history to retrieve information from KeepGoing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about past work sessions without any side effects. It performs a read-only query operation similar to 'get' or 'list' operations, making it a Read category tool. The severity is low because retrieving session history poses minimal risk—it cannot alter state, execute code, delete data, or commit financial transactions.
From the tool's definition Tool description states 'Get recent session checkpoints' and 'Returns a chronological list' — both query/retrieval operations with no modification or execution capability.
Attacks that exploit this kind of access
Get recent session checkpoints. Returns a chronological list of what the developer worked on. It is categorised as a Read tool in the KeepGoing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KeepGoing MCP Server 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 KeepGoing MCP Server. 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 KeepGoing MCP Server MCP server (keepgoing-dev/mcp-server). 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 →