Cancel a Tendem task. Costs are not refunded after approval.
AI agents call cancel_task to permanently remove resources in Tendem MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While this tool could be categorized as Financial due to the cost implications mentioned, the primary action is irreversibly cancelling an approved task without refund capability. This makes it Destructive (irreversible state change) rather than purely Financial. The high severity reflects that an AI agent misusing this could cancel important tasks and cause unrecoverable financial losses.
From the tool's definition Tool description states 'Cancel a Tendem task. Costs are not refunded after approval.' This irreversibly cancels a task and explicitly notes that financial costs cannot be recovered, making it a non-undoable action with financial implications.
Attacks that exploit this kind of access
Cancel a Tendem task. Costs are not refunded after approval. It is categorised as a Destructive tool in the Tendem MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tendem 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 Tendem MCP. Nothing to install.
cancel_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_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_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_task is provided by the Tendem MCP server (toloka/tendem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.