AI agents call list_change_orders_by_origin 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 |
|---|---|---|---|
appName | string | — | Application name filter. Use list_applications to discover valid app names. |
envName | string | — | Environment name filter. Use list_environments to discover valid environment names for an application. |
originId | string | Yes | Origin identifier from the source system. For FLOW origin, use a pipeline run ID or pipeline ID. |
originType | string | Yes | Origin type indicating the source system. Valid value: FLOW (Flow pipeline). |
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 retrieves and queries historical change order data filtered by origin, enabling audit and tracing workflows. It performs no creation, modification, deletion, or external execution. The blast radius of misuse is minimal—an agent could only retrieve existing records, not alter state or trigger actions.
From the tool's definition Tool name contains 'list' and description states it 'List[s] AppStack change orders by creation origin' and 'trace deployments' — both passive retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
List AppStack change orders by creation origin. Use this to trace deployments back to their source (e.g., a Flow pipeline). It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_change_orders_by_origin accepts 5 parameters: appName, envName, originId, originType, organizationId. Required: originId, originType. 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_change_orders_by_origin: 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_change_orders_by_origin 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_change_orders_by_origin 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_change_orders_by_origin. 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_change_orders_by_origin 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 →