AI agents invoke codemagic_start_build to trigger actions in Codemagic. 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.
codemagic_start_build triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Trigger a new build for a workflow on a given branch or tag. Either branch or tag must be provided. Returns the new build identifier. It is categorised as a Execute tool in the Codemagic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Codemagic MCP server in PolicyLayer and add a rule for codemagic_start_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_start_build 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 codemagic_start_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_start_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_start_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.