AI agents call list_change_order_versions 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 | Yes | Application name. Use list_applications to discover valid app names. |
current | number | — | Page number for pagination. Starts at 1. |
creators | string | — | Comma-separated creator account IDs. |
envNames | string | — | Comma-separated environment names. Use list_environments to discover valid environment names for an application. |
pageSize | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
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 historical version information about change orders (deployment records). It performs a read-only query operation with no side effects, no irreversible actions, and no code execution. The data returned is metadata about past deployments, not triggering new deployments or modifications.
From the tool's definition Tool name contains 'list' and description states it 'List[s] AppStack change order versions' and 'track[s] actual deployments' — purely informational retrieval with no modification, deletion, or execution of changes.
Attacks that exploit this kind of access
List AppStack change order versions. Change orders track actual deployments and their versions. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_change_order_versions accepts 6 parameters: appName, current, creators, envNames, pageSize, organizationId. Required: appName. 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_order_versions: 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_order_versions 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_order_versions 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_order_versions. 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_order_versions 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 →