Rewind the current branch to a specific checkpoint commit. ⚠️ Destructive: rewrites git history on the current branch. Use \
AI agents call entire_checkpoint_rewind to permanently remove resources in Entire — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly rewrites git history, which is an irreversible destructive operation. Rewriting branch history can permanently discard commits and cannot be undone without external backups, making it critical severity.
From the tool's definition 'Rewind the current branch to a specific checkpoint commit' and '⚠️ Destructive: rewrites git history on the current branch'
Attacks that exploit this kind of access
Rewind the current branch to a specific checkpoint commit. ⚠️ Destructive: rewrites git history on the current branch. Use \. It is categorised as a Destructive tool in the Entire MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Entire MCP server in PolicyLayer and add a rule for entire_checkpoint_rewind: 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_rewind is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the entire_checkpoint_rewind 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_rewind. 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_rewind 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 →