cancel_instance_task
Cancel a task on the registered local or managed browser runtime for a private instance.
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
Attacks that exploit this kind of access
The rule that runs cancel_instance_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_instance_task, this is the rule to start with:
cancel_instance_task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every cancel_instance_task call is checked against it from then on.
Questions about cancel_instance_task
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.
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.
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.
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.
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.
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.
Across the catalogue