AI agents call runway_cancelTask to permanently remove resources in Runway API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes or terminates a task, which fits the Destructive category definition. While not as severe as a cascade delete, canceling a task in a video generation context destroys the task record/state and prevents its completion. The blast radius is high because an AI agent could cancel critical generation jobs without authorization or verification, causing loss of work and wasted resources.
From the tool's definition Tool description states it 'Deletes or cancels a given task.' The verb 'deletes' combined with the irreversible nature of task cancellation indicates data destruction that cannot be undone.
Documented attack patterns abuse exactly the kind of access runway_cancelTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runway API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for runway_cancelTask:
{
"version": "1",
"default": "deny",
"hide": [
"runway_cancelTask"
]
} runway_cancelTask disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes or cancels a given task. It is categorised as a Destructive tool in the Runway API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Runway API MCP Server MCP server in PolicyLayer and add a rule for runway_cancelTask: 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 Runway API MCP Server. Nothing to install.
runway_cancelTask 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 runway_cancelTask 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 runway_cancelTask. 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.
runway_cancelTask is provided by the Runway API MCP Server MCP server (runwayml/runway-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runway API MCP Server, 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.
7 Runway API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.