cancel_warmup
Stop a warm-up at the end of its paid period (no refund; ends immediately if unpaid). resume_warmup undoes a pending cancellation.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/cancel-warmup.md
What cancel_warmup does on Max MCP Server
AI agents call cancel_warmup to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_warmup is rated Critical
An AI agent that decides to call cancel_warmup doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Max MCP Server is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cancel_warmup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_warmup, this is the rule to start with:
cancel_warmup 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 Max MCP Server, apply this rule, and every cancel_warmup call is checked against it from then on.
Questions about cancel_warmup
Stop a warm-up at the end of its paid period (no refund; ends immediately if unpaid). resume_warmup undoes a pending cancellation. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for cancel_warmup: 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 Max MCP Server. Nothing to install.
cancel_warmup 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_warmup 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_warmup. 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_warmup is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue