AI agents call list_app_release_stage_runs 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 |
|---|---|---|---|
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. |
nextToken | string | — | Keyset pagination token from the previous response. |
pagination | string | — | Pagination mode. Valid value: keyset. |
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 historical execution records without modifying, deleting, or executing operations. It is a pure read operation that returns data about past deployment runs. The low severity reflects that listing historical records poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states 'List AppStack release stage execution records' with no mention of modifications, deletions, or side effects. It retrieves deployment stage run history.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
List AppStack release stage execution records. Each record represents a single run of a deployment stage. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_app_release_stage_runs accepts 10 parameters: page, sort, appName, orderBy, perPage, nextToken, pagination, organizationId, releaseStageSn, releaseWorkflowSn. Required: 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_app_release_stage_runs: 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_app_release_stage_runs 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_app_release_stage_runs 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_app_release_stage_runs. 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_app_release_stage_runs 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 →