Critical Risk →

crawl_cancel

Mark a crawl job as cancelled. Returns immediately. Subsequent

How to control crawl_cancel ↓

AI agents call crawl_cancel 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.

Critical Risk

An AI agent that decides to call crawl_cancel doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from OpenChrome is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access crawl_cancel 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 crawl_cancel:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "crawl_cancel"
  ]
}

crawl_cancel disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register OpenChrome — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the crawl_cancel tool do? +

Mark a crawl job as cancelled. Returns immediately. Subsequent. 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.

How do I enforce a policy on crawl_cancel? +

Register the OpenChrome MCP server in PolicyLayer and add a rule for crawl_cancel: 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.

What risk level is crawl_cancel? +

crawl_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit crawl_cancel? +

Yes. Add a rate_limit block to the crawl_cancel 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.

How do I block crawl_cancel completely? +

Set action: deny in the PolicyLayer policy for crawl_cancel. 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.

What MCP server provides crawl_cancel? +

crawl_cancel 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.

Enforce policy on every OpenChrome tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.