ci_get_build_status

What ci_get_build_status does on Mimi Seed

AI agents call ci_get_build_status to retrieve information from Mimi Seed without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ci_get_build_status is rated Low

This is a pure read operation that queries the status of an existing build. It has no side effects—it only retrieves information. No code execution, data modification, or destructive action is involved. The blast radius from misuse is minimal: an attacker might learn about build failure or success status, but cannot trigger builds, modify code, or cause financial harm.

From the tool's definition Tool name and description indicate 'get build status' / 조회합니다 (retrieve/query). The function retrieves the current state of a CI/CD build (GitHub Actions run or GitLab pipeline) without modifying, executing, or deleting anything.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ci_get_build_status": {}
  }
}

Questions about ci_get_build_status