operator_work_cancel
Run operator-work.cancel through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/operator-work-cancel.md
What operator_work_cancel does on Appaloft
AI agents call operator_work_cancel to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | Yes | |
workId | string | Yes |
Parameters from the server's own tool schema.
Why operator_work_cancel is rated Critical
An AI agent that decides to call operator_work_cancel doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Appaloft is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs operator_work_cancel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For operator_work_cancel, this is the rule to start with:
operator_work_cancel 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 Appaloft, apply this rule, and every operator_work_cancel call is checked against it from then on.
Questions about operator_work_cancel
Run operator-work.cancel through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
operator_work_cancel accepts 2 parameters: reason, workId. Required: reason, workId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for operator_work_cancel: 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 Appaloft. Nothing to install.
operator_work_cancel 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 operator_work_cancel 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 operator_work_cancel. 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.
operator_work_cancel is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue