ci_trigger_build
A execute tool on the Mimi Seed MCP server.
This record as markdown: /tools/yoonion-mimi-seed-mcp/ci-trigger-build.md
What ci_trigger_build does on Mimi Seed
AI agents invoke ci_trigger_build to trigger actions in Mimi Seed. 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.
Why ci_trigger_build is rated High
A CI trigger tool runs code and initiates automated build/deployment workflows—classic Execute category behavior. The blast radius is high because a malicious agent could trigger builds for arbitrary app versions, sign them with compromised credentials, or deploy to production stores without authorization.
From the tool's definition Tool name 'ci_trigger_build' indicates triggering a CI/CD pipeline build process. The sibling tools include 'android_generate_keystore', 'android_signing_setup', and 'appstore_attach_build', which establish this server's focus on mobile app build and…
Attacks that exploit this kind of access
The rule that runs ci_trigger_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mimi Seed, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ci_trigger_build, this is the rule to start with:
ci_trigger_build 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 Mimi Seed, apply this rule, and every ci_trigger_build call is checked against it from then on.
Questions about ci_trigger_build
ci_trigger_build is a execute tool on the Mimi Seed MCP server. It is categorised as a Execute tool in the Mimi Seed MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for ci_trigger_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 Mimi Seed. Nothing to install.
ci_trigger_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 ci_trigger_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 ci_trigger_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.
ci_trigger_build is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mimi Seed, and thousands of servers like it.
Across the catalogue