AI agents call list_appstack_change_request_executions 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 |
|---|---|---|---|
sn | string | Yes | Change request serial number. Typically discovered via list_attached_change_requests. |
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction. Valid values: asc, desc. |
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
orderBy | string | — | Sort field. Valid values: id, gmtCreate. |
perPage | 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. |
releaseStageSn | string | Yes | Release stage serial number. Use list_app_release_stage_briefs to discover valid values. |
releaseWorkflowSn | string | Yes | Release workflow serial number. Use list_app_release_workflows to discover valid values. |
Parameters from the server's own tool schema.
This tool queries and retrieves execution history for change requests. It has no side effects, does not execute deployments, and does not modify state. It is a read-only operation appropriate for auditing and monitoring purposes. The low severity reflects minimal blast radius if misused by an AI agent — it only exposes historical deployment metadata.
From the tool's definition Tool name contains 'list' and description states it 'List execution records' — a retrieval operation with no modification or execution of deployments.
Attacks that exploit this kind of access
List execution records for an AppStack change request. Change requests track planned deployments. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_appstack_change_request_executions accepts 9 parameters: sn, page, sort, appName, orderBy, perPage, organizationId, releaseStageSn, releaseWorkflowSn. Required: sn, appName, releaseStageSn, releaseWorkflowSn. 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_appstack_change_request_executions: 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_appstack_change_request_executions 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_appstack_change_request_executions 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_appstack_change_request_executions. 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_appstack_change_request_executions 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 →