# ci_get_build_status

특정 빌드(GitHub Actions run / GitLab pipeline)의 현재 상태를 조회합니다.

Agent View of the PolicyLayer registry record for `ci_get_build_status`. HTML page: https://policylayer.com/tools/yoonion-mimi-seed-mcp/ci-get-build-status

## Facts

- Tool: `ci_get_build_status`
- Server: Mimi Seed (`@yoonion/mimi-seed-mcp`) — https://policylayer.com/tools/yoonion-mimi-seed-mcp.md
- Install: `npx -y @yoonion/mimi-seed-mcp`
- Homepage: git+https://github.com/jeonghwanko/mimi-seed-sdk.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ci_get_build_status",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mimi Seed:

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

## Other tools on Mimi Seed (229)

- `appstore_cancel_review` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-cancel-review.md
- `appstore_delete_preview` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-delete-preview.md
- `appstore_delete_product` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-delete-product.md
- `appstore_delete_screenshot` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-delete-screenshot.md
- `appstore_delete_screenshot_set` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-delete-screenshot-set.md
- `appstore_remove_review_submission_item` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-remove-review-submission-item.md
- `ci_cancel_build` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/ci-cancel-build.md
- `firebase_delete_android_app` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/firebase-delete-android-app.md
- `firebase_delete_ios_app` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/firebase-delete-ios-app.md
- `firebase_delete_web_app` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/firebase-delete-web-app.md
- `jenkins_delete_credential` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/jenkins-delete-credential.md
- `playstore_cancel_recovery_action` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-cancel-recovery-action.md
- `playstore_delete_all_images` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-delete-all-images.md
- `playstore_delete_product` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-delete-product.md
- `playstore_delete_service_account` — Destructive — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-delete-service-account.md
- `android_generate_keystore` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/android-generate-keystore.md
- `android_signing_setup` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/android-signing-setup.md
- `appstore_release_version` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-release-version.md
- `appstore_submit_beta_review` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-submit-beta-review.md
- `appstore_submit_for_review` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/appstore-submit-for-review.md
- `bigquery_run_query` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/bigquery-run-query.md
- `ci_trigger_build` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/ci-trigger-build.md
- `jenkins_update_job` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/jenkins-update-job.md
- `mimi_seed_auth_start` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/mimi-seed-auth-start.md
- `playstore_deploy_recovery_action` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-deploy-recovery-action.md
- `playstore_promote_release` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-promote-release.md
- `video_build_timeline` — Execute — https://policylayer.com/tools/yoonion-mimi-seed-mcp/video-build-timeline.md
- `gcp_create_budget` — Financial — https://policylayer.com/tools/yoonion-mimi-seed-mcp/gcp-create-budget.md
- `playstore_get_financial_report` — Financial — https://policylayer.com/tools/yoonion-mimi-seed-mcp/playstore-get-financial-report.md
- `admob_get_report` — Read — https://policylayer.com/tools/yoonion-mimi-seed-mcp/admob-get-report.md
- …and 199 more: https://policylayer.com/tools/yoonion-mimi-seed-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=yoonion-mimi-seed-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/yoonion-mimi-seed-mcp