AI agents call list_app_release_stage_exec_metadata 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. |
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. |
executionNumber | string | Yes | Release stage execution number. Use list_app_release_stage_runs 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 metadata information (linked work items and commits) associated with a release stage execution. It has no side effects, does not modify data, does not execute code or trigger external operations, and does not delete anything. It is purely informational read access to DevOps pipeline metadata.
From the tool's definition Tool name contains 'list' and description states 'List integrated change metadata' — retrieves metadata about release stage execution including work items and commits. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List integrated change metadata for an AppStack release stage execution. Metadata includes linked work items and commits. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_app_release_stage_exec_metadata accepts 5 parameters: appName, organizationId, releaseStageSn, executionNumber, releaseWorkflowSn. Required: appName, releaseStageSn, executionNumber, 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_exec_metadata: 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_exec_metadata 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_exec_metadata 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_exec_metadata. 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_exec_metadata 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 →