AI agents call list_app_release_workflows 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. |
Parameters from the server's own tool schema.
This tool retrieves and queries existing release workflow data without side effects. It enables viewing deployment pipeline configurations and status, which is a read-only operation. The low severity reflects that listing workflows poses minimal risk; an AI agent misusing this would at worst retrieve information it shouldn't see, not trigger unintended deployments or data loss.
From the tool's definition Tool name contains 'list' and description explicitly states it 'List[s] AppStack release workflows' with no mention of modification, deletion, or execution of deployments—only retrieval and inspection of workflow metadata.
Attacks that exploit this kind of access
List AppStack release workflows for an application. Release workflows model multi-stage deployment pipelines. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_app_release_workflows accepts 2 parameters: appName, organizationId. Required: appName. 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_workflows: 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_workflows 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_workflows 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_workflows. 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_workflows 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 →