AI agents call entire_checkpoint_list to retrieve information from Entire without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays checkpoint metadata without modifying, deleting, or executing anything. It is a pure read operation that queries existing data from the repository. The blast radius if misused is minimal — an agent could only enumerate checkpoints, not alter them.
From the tool's definition Tool description states 'List all Entire checkpoints' — a retrieval operation with no side effects. The name 'entire_checkpoint_list' and the phrase 'in reverse chronological order' confirm this is a query/list action.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all Entire checkpoints for the current repo in reverse chronological order. Uses \. It is categorised as a Read tool in the Entire MCP Server, which means it retrieves data without modifying state.
Register the Entire MCP server in PolicyLayer and add a rule for entire_checkpoint_list: 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 Entire. Nothing to install.
entire_checkpoint_list 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 entire_checkpoint_list 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 entire_checkpoint_list. 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.
entire_checkpoint_list is provided by the Entire MCP server (jurislm/entire-mcp). 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 →