Cancel a build that is queued or in progress. If the build has already finished, returns a message indicating so.
AI agents call codemagic_cancel_build to permanently remove resources in Codemagic — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call codemagic_cancel_build doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Codemagic is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Cancel a build that is queued or in progress. If the build has already finished, returns a message indicating so. It is categorised as a Destructive tool in the Codemagic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codemagic MCP server in PolicyLayer and add a rule for codemagic_cancel_build: 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 Codemagic. Nothing to install.
codemagic_cancel_build 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 codemagic_cancel_build 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 codemagic_cancel_build. 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.
codemagic_cancel_build is provided by the Codemagic MCP server (zfinix/codemagic_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.