ci_list_recent_builds

최근 빌드 목록을 조회합니다. 특정 브랜치나 워크플로로 필터링 가능.

SERVERMimi Seed SOURCE@yoonion/mimi-seed-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yoonion-mimi-seed-mcp/ci-list-recent-builds.md

WHAT IT DOES

What ci_list_recent_builds does on Mimi Seed

AI agents call ci_list_recent_builds 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.

RISK

Why ci_list_recent_builds is rated Low

This tool queries and retrieves historical build information without modifying, executing, or deleting any data. It is a read-only operation that returns metadata about CI builds. No destructive, financial, or executable actions are performed.

From the tool's definition Tool name 'ci_list_recent_builds' and description 'retrieves recent build list' with filtering by branch/workflow indicate a query/list operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ci_list_recent_builds Allowed

ci_list_recent_builds is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY 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_list_recent_builds call is checked against it from then on.

FAQ

Questions about ci_list_recent_builds

What does the ci_list_recent_builds tool do? +

최근 빌드 목록을 조회합니다. 특정 브랜치나 워크플로로 필터링 가능. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ci_list_recent_builds? +

Register the Mimi Seed MCP server in PolicyLayer and add a rule for ci_list_recent_builds: 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_list_recent_builds? +

ci_list_recent_builds is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ci_list_recent_builds? +

Yes. Add a rate_limit block to the ci_list_recent_builds 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_list_recent_builds completely? +

Set action: deny in the PolicyLayer policy for ci_list_recent_builds. 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_list_recent_builds? +

ci_list_recent_builds 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →