ci_cancel_build

진행 중인 빌드를 취소합니다. (GitHub Actions run / GitLab pipeline)

SERVERMimi Seed SOURCE@yoonion/mimi-seed-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yoonion-mimi-seed-mcp/ci-cancel-build.md

WHAT IT DOES

What ci_cancel_build does on Mimi Seed

AI agents call ci_cancel_build to permanently remove resources in Mimi Seed, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why ci_cancel_build is rated Critical

Cancelling a CI build is an irreversible action: once cancelled, the build run cannot be resumed. This is a destructive operation with a medium blast radius — it can interrupt deployments or release pipelines, but does not delete code or data.

From the tool's definition 진행 중인 빌드를 취소합니다 (Cancel an in-progress build — GitHub Actions run / GitLab pipeline)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ci_cancel_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_cancel_build, this is the rule to start with:

ci_cancel_build Hidden

ci_cancel_build is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "ci_cancel_build"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mimi Seed, apply this rule, and every ci_cancel_build call is checked against it from then on.

FAQ

Questions about ci_cancel_build

What does the ci_cancel_build tool do? +

진행 중인 빌드를 취소합니다. (GitHub Actions run / GitLab pipeline). It is categorised as a Destructive tool in the Mimi Seed MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on ci_cancel_build? +

Register the Mimi Seed MCP server in PolicyLayer and add a rule for ci_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 Mimi Seed. Nothing to install.

What risk level is ci_cancel_build? +

ci_cancel_build is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ci_cancel_build? +

Yes. Add a rate_limit block to the ci_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.

How do I block ci_cancel_build completely? +

Set action: deny in the PolicyLayer policy for ci_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.

What MCP server provides ci_cancel_build? +

ci_cancel_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.

KEEP EXPLORING

More on Mimi Seed, and thousands of servers like it.

This server

All 230 Mimi Seed tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →