AI agents call get_latest_pipeline_run 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 |
|---|---|---|---|
pipelineId | string | Yes | Pipeline ID (string). Use list_pipelines to find the pipeline ID. |
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 queries and retrieves metadata about the most recent pipeline run. It performs a read-only lookup operation with no capability to modify, delete, or execute actions. The phrasing 'Get' and 'status check' confirms it is informational only. Blast radius is minimal — an agent could learn operational details but cannot trigger deployments or alter state.
From the tool's definition Tool description states 'Get the latest execution run' and 'quick status check' — retrieves pipeline execution status without modification or side effects.
Attacks that exploit this kind of access
Get the latest execution run for a Flow pipeline. Use this for a quick status check without listing all historical runs. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_latest_pipeline_run accepts 2 parameters: pipelineId, 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_latest_pipeline_run: 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_latest_pipeline_run 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_latest_pipeline_run 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_latest_pipeline_run. 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_latest_pipeline_run 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 →