deployments_cancel
Run deployments.cancel through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/deployments-cancel.md
What deployments_cancel does on Appaloft
AI agents invoke deployments_cancel to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | string | Yes | |
resourceId | string | — | |
deploymentId | string | Yes |
Parameters from the server's own tool schema.
Why deployments_cancel is rated High
Cancelling a deployment triggers an external operation that interrupts an in-progress process. This is an Execute-category action since it triggers a side-effecting operation on a running deployment. While it may not permanently destroy data, it can interrupt critical deployment pipelines and cause service disruption, warranting high severity.
From the tool's definition 'deployments_cancel' - cancels a running deployment operation; 'Run deployments.cancel through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs deployments_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 deployments_cancel, this is the rule to start with:
deployments_cancel stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every deployments_cancel call is checked against it from then on.
Questions about deployments_cancel
Run deployments.cancel through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
deployments_cancel accepts 3 parameters: confirm, resourceId, deploymentId. Required: confirm, deploymentId. 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 deployments_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.
deployments_cancel is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deployments_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 deployments_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.
deployments_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