AI agents call get_app_orchestration 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 | Orchestration serial number. Use list_app_orchestration to discover valid serial numbers. |
sha | string | — | Optional SHA to retrieve a specific version of the orchestration. |
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
tagName | string | — | Optional tag name to retrieve a tagged version of the orchestration. |
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 existing orchestration data by identifier and returns information without creating, modifying, deleting, or executing any operations. It is purely informational and poses minimal risk if misused by an AI agent, as the worst case is unauthorized information disclosure about an existing AppStack orchestration configuration.
From the tool's definition The tool description states 'Get an AppStack orchestration by serial number', which is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get an AppStack orchestration by serial number. Use list_app_orchestration to discover valid serial numbers. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_app_orchestration accepts 5 parameters: sn, sha, appName, tagName, organizationId. Required: sn, 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 get_app_orchestration: 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_orchestration 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_orchestration 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_orchestration. 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_orchestration 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 →