New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cancel_instance_task

Cancel a task on the registered local or managed browser runtime for a private instance.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/cancel-instance-task.md

What cancel_instance_task does on ProAgentStore

AI agents call cancel_instance_task to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cancel_instance_task is rated Critical

Cancelling a running task is an irreversible action — the in-progress work is terminated and cannot be resumed. This goes beyond a simple write/update, as the task execution state is permanently aborted. Misuse by an AI agent could interrupt critical workflows on private instances, making the blast radius high.

From the tool's definition Cancel a task on the registered local or managed browser runtime for a private instance

Questions about cancel_instance_task

What does the cancel_instance_task tool do? +

Cancel a task on the registered local or managed browser runtime for a private instance. It is categorised as a Destructive tool in the ProAgentStore 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_instance_task? +

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

What risk level is cancel_instance_task? +

cancel_instance_task 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_instance_task? +

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

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

cancel_instance_task is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ProAgentStore, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ProAgentStore's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.