Save, load, list, or delete automation checkpoints for long-running session continuity.
AI agents call oc_checkpoint to permanently remove resources in OpenChrome — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool supports multiple operations including 'delete' of checkpoints, which is irreversible. Since the most severe applicable category must be chosen, and deletion of checkpoints cannot be undone, this classifies as Destructive. Severity is medium because checkpoints are session artifacts rather than primary data, but losing them could disrupt long-running automations.
From the tool's definition 'Save, load, list, or delete automation checkpoints for long-running session continuity'
Documented attack patterns abuse exactly the kind of access oc_checkpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for oc_checkpoint:
{
"version": "1",
"default": "deny",
"hide": [
"oc_checkpoint"
]
}oc_checkpoint disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Save, load, list, or delete automation checkpoints for long-running session continuity. It is categorised as a Destructive tool in the OpenChrome MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_checkpoint: 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 OpenChrome. Nothing to install.
oc_checkpoint 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 oc_checkpoint 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 oc_checkpoint. 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.
oc_checkpoint is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.