Get a comprehensive overview of an Appstack system release including basic info, members, products, and attached change requests in one read-only call. Use this after discovering a release via search_releases or list_system_release_workflows.
AI agents call get_release_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 |
|---|---|---|---|
sn | string | Yes | Release serial number. Use search_releases or list_system_release_workflows to discover valid serial numbers. |
systemName | string | Yes | System name. Use list_systems to discover valid names. |
includeMembers | boolean | — | Whether to include release members. Defaults to true. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
includeProducts | boolean | — | Whether to include release products. Defaults to true. |
changeRequestLimit | number | — | Max change requests returned. Defaults to 5. |
includeChangeRequests | boolean | — | Whether to include attached change requests. Defaults to true. |
Parameters from the server's own tool schema.
This tool queries and retrieves release metadata without any capability to modify, delete, execute commands, or trigger financial transactions. The explicit 'read-only' designation and the nature of the returned data (basic info, members, products, change requests) confirm it performs information retrieval only.
From the tool's definition Tool description explicitly states 'read-only call' and retrieves 'overview' of release information including 'basic info, members, products, and attached change requests' — all data retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Get a comprehensive overview of an Appstack system release including basic info, members, products, and attached change requests in one read-only call. Use this after discovering a release via search_releases or list_system_release_workflows. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_release_overview accepts 7 parameters: sn, systemName, includeMembers, organizationId, includeProducts, changeRequestLimit, includeChangeRequests. Required: sn, systemName. 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_release_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_release_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_release_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_release_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_release_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 →