AI agents call list_release_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 | Release serial number. Use search_releases or list_system_release_workflows to discover valid serial numbers. |
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction. Valid values: asc, desc. |
orderBy | string | — | Sort field. Valid values: id, gmtCreate. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
systemName | string | Yes | System name. Use list_systems to discover valid names. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
releaseStageSn | string | Yes | Release stage serial number. Use list_system_release_workflows to discover valid serial numbers. |
releaseWorkflowSn | string | Yes | Release workflow serial number. Use list_system_release_workflows to discover valid serial numbers. |
Parameters from the server's own tool schema.
This tool retrieves and lists historical execution records for release workflows in a DevOps platform. It has no capability to modify, delete, or trigger operations—it only queries and returns existing data. The blast radius of misuse is minimal; an agent could at most access execution logs and records that may contain sensitive information, but cannot cause system changes or harm.
From the tool's definition Tool name 'list_release_executions' and description 'List execution records' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
List execution records for an AppStack system release. Use this after discovering release workflow and stage details via list_system_release_workflows or get_release_overview. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_release_executions accepts 9 parameters: sn, page, sort, orderBy, perPage, systemName, organizationId, releaseStageSn, releaseWorkflowSn. Required: sn, systemName, 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_release_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_release_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_release_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_release_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_release_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 →