List Flow CI/CD pipelines in a Yunxiao organization. Use this to discover pipelines and obtain their IDs before calling pipeline-scoped tools. For a comprehensive view of a single pipeline including latest run and history, use get_pipeline_overview instead.
AI agents call list_pipelines to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
perPage | number | — | Page size for pagination. Yunxiao supports up to 30. |
statusList | string | — | Comma-separated pipeline statuses. Common values: RUNNING, SUCCESS, FAIL, CANCELED, WAITING. |
pipelineName | string | — | Filter by pipeline name (contains match). |
createEndTime | number | — | Pipeline creation end time as a Unix timestamp in milliseconds. |
executeEndTime | number | — | Pipeline execution end time as a Unix timestamp in milliseconds. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
createStartTime | number | — | Pipeline creation start time as a Unix timestamp in milliseconds (e.g., 1704067200000). |
executeStartTime | number | — | Pipeline execution start time as a Unix timestamp in milliseconds. |
Parameters from the server's own tool schema.
This tool queries and returns a list of CI/CD pipelines from the Yunxiao DevOps platform. It retrieves data without modifying, executing, deleting, or committing any resources. The stated purpose is discovery and enumeration to support other operations. No destructive, financial, or execution capabilities are present.
From the tool's definition Tool name: list_pipelines. Description states 'List Flow CI/CD pipelines' and 'discover pipelines and obtain their IDs' — purely informational retrieval with no side effects.
Attacks that exploit this kind of access
List Flow CI/CD pipelines in a Yunxiao organization. Use this to discover pipelines and obtain their IDs before calling pipeline-scoped tools. For a comprehensive view of a single pipeline including latest run and history, use get_pipeline_overview instead. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_pipelines accepts 9 parameters: page, perPage, statusList, pipelineName, createEndTime, executeEndTime, organizationId, createStartTime, executeStartTime. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for list_pipelines: 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 Yunxiao. Nothing to install.
list_pipelines 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 list_pipelines 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 list_pipelines. 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.
list_pipelines is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →