Critical Risk →

cancel_task

取消执行中的任务

How to control cancel_task ↓

What cancel_task does on Openaaas Mcp Adapter

AI agents call cancel_task to permanently remove resources in Openaaas Mcp Adapter — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why cancel_task needs a policy

Cancelling a running task is irreversible — the task's execution state and any intermediate progress are permanently terminated and cannot be resumed. This maps to Destructive. Severity is medium because the blast radius is limited to losing a single task's in-progress work rather than deleting stored data or files.

From the tool's definition 取消执行中的任务 (Cancel an in-progress/executing task)

Documented attack patterns abuse exactly the kind of access cancel_task gives an agent:

How to control cancel_task

PolicyLayer is an MCP gateway — it sits between your AI agents and Openaaas Mcp Adapter, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_task:

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

cancel_task 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 Openaaas Mcp Adapter — 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.

Related tools and policies

Go deeper

Questions about cancel_task

What does the cancel_task tool do? +

取消执行中的任务. It is categorised as a Destructive tool in the Openaaas Mcp Adapter 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_task? +

Register the Openaaas Mcp Adapter MCP server in PolicyLayer and add a rule for cancel_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 Openaaas Mcp Adapter. Nothing to install.

What risk level is cancel_task? +

cancel_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_task? +

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

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

cancel_task is provided by the Openaaas Mcp Adapter MCP server (wolido/openaaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openaaas Mcp Adapter tool call.

Start from Openaaas Mcp Adapter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

16 Openaaas Mcp Adapter tools catalogued and risk-classified — across an index of 43,000+ 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.