AI agents call list_app_release_stage_briefs 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. |
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 retrieves and presents existing data about release stages in a DevOps workflow. There are no side effects, no data modification, no code execution, and no destructive operations. The blast radius of misuse is minimal — an attacker could only gain visibility into deployment pipeline structure, which is informational. Confidence is high because the name and description are unambiguous.
From the tool's definition Tool name contains 'list' and description states 'List AppStack release stage briefs' — a query operation that retrieves deployment phase information without modifying or executing anything.
Attacks that exploit this kind of access
List AppStack release stage briefs for an application release workflow. Stages represent individual deployment phases within a workflow. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_app_release_stage_briefs accepts 3 parameters: appName, organizationId, releaseWorkflowSn. Required: appName, 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_briefs: 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_briefs 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_briefs 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_briefs. 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_briefs 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 →