Cancel a pending or running background task
AI agents call cancel_async_task to permanently remove resources in Odoo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a background task is an irreversible action — once cancelled, the task's execution is terminated and cannot be resumed. This goes beyond a simple write/update since the task state transition to 'cancelled' typically cannot be undone, and any work-in-progress by that task is lost.
From the tool's definition Cancel a pending or running background task
Attacks that exploit this kind of access
Cancel a pending or running background task. It is categorised as a Destructive tool in the Odoo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for cancel_async_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 Odoo MCP Server. Nothing to install.
cancel_async_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_async_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_async_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_async_task is provided by the Odoo MCP Server MCP server (pypi:odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.