AI agents call get_pipeline_overview 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 |
|---|---|---|---|
runLimit | number | — | Max recent runs returned. Defaults to 5. |
pipelineId | string | Yes | Pipeline ID (string). Use list_pipelines to find the pipeline ID. |
includeRuns | boolean | — | Whether to include recent run history. Defaults to true. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool performs only data retrieval operations on pipeline metadata and execution history. The explicit 'read-only' designation and absence of any modification, deletion, or execution capabilities clearly place it in the Read category with low severity, as there are no side effects or blast radius from its use.
From the tool's definition Tool description explicitly states 'read-only call' and retrieves 'comprehensive overview' including 'basic info, latest run, and recent run history' — all query/retrieval operations with no mutations.
Attacks that exploit this kind of access
Get a comprehensive overview of a Flow pipeline including basic info, latest run, and recent run history in one read-only call. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_pipeline_overview accepts 4 parameters: runLimit, pipelineId, includeRuns, organizationId. Required: pipelineId. 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 get_pipeline_overview: 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.
get_pipeline_overview 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 get_pipeline_overview 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 get_pipeline_overview. 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.
get_pipeline_overview 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 →