AI agents call ci_get_build_status to retrieve information from Mimi Seed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
특정 빌드(GitHub Actions run / GitLab pipeline)의 현재 상태를 조회합니다. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for ci_get_build_status: 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_get_build_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ci_get_build_status 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_get_build_status. 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_get_build_status 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.
ci_get_build_status is one line of Mimi Seed's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →