Get a comprehensive overview of an AppStack application release workflow including workflow info and stage briefs in one read-only call. Use this after discovering a workflow via list_app_release_workflows.
AI agents call get_app_release_workflow_overview 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. |
includeStageBriefs | boolean | — | Whether to include stage briefs. Defaults to true. |
Parameters from the server's own tool schema.
This tool retrieves workflow metadata and stage information without modifying, executing, or deleting any resources. It is a query operation on a DevOps platform that returns informational data about application release workflows. The "read-only" designation confirms no side effects or state changes occur.
From the tool's definition The tool description explicitly states it is a "read-only call" that retrieves "comprehensive overview of an AppStack application release workflow including workflow info and stage briefs".
Attacks that exploit this kind of access
Get a comprehensive overview of an AppStack application release workflow including workflow info and stage briefs in one read-only call. Use this after discovering a workflow via list_app_release_workflows. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_app_release_workflow_overview accepts 4 parameters: appName, organizationId, releaseWorkflowSn, includeStageBriefs. 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 get_app_release_workflow_overview: 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.
get_app_release_workflow_overview 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 get_app_release_workflow_overview 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 get_app_release_workflow_overview. 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.
get_app_release_workflow_overview 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 →