Critical Risk →

cancel_interrupt

Cancel a pending interrupt request. Use when the agent no longer needs the decision.

Part of the Loopin server.

cancel_interrupt can permanently delete data in Loopin, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LOOPIN →

Free to start. No card required.

AI agents may call cancel_interrupt to permanently remove or destroy resources in Loopin. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cancel_interrupt in a loop, permanently destroying resources in Loopin. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

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

See the full Loopin policy for all 6 tools.

Get this rule live on your own Loopin server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LOOPIN →

These attack patterns abuse exactly the kind of access cancel_interrupt gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cancel_interrupt only ever does what you allow.

SECURE LOOPIN →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cancel_interrupt tool do? +

Cancel a pending interrupt request. Use when the agent no longer needs the decision.. It is categorised as a Destructive tool in the Loopin 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 cancel_interrupt? +

Register the Loopin MCP server in PolicyLayer and add a rule for cancel_interrupt: 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 Loopin. Nothing to install.

What risk level is cancel_interrupt? +

cancel_interrupt 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 cancel_interrupt? +

Yes. Add a rate_limit block to the cancel_interrupt 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 cancel_interrupt completely? +

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

cancel_interrupt is provided by the Loopin MCP server (nicholasemccormick/loopin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Loopin tool call.

Deterministic rules across all 6 Loopin tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.