AI agents call search_releases 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 |
|---|---|---|---|
sort | string | — | Sort direction. Valid values: asc, desc. |
states | array | — | Release states filter. Valid values: DEVELOPING, RELEASING, CLOSED, RELEASED. |
orderBy | string | — | Sort field. Valid values: id, gmt_create. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
nextToken | string | — | Keyset pagination token from the previous response. |
pagination | string | — | Pagination mode. Valid value: keyset. |
systemName | string | — | System unique name. Use list_systems to discover valid names. |
nameKeyword | string | — | Release display-name search keyword. |
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 or queries release information from the Yunxiao DevOps platform to help users find and discover releases. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius is minimal: misuse would only expose information about releases that an authorized user could already access through the platform. Categorized as Read with low severity.
From the tool's definition Tool name and description both indicate a search/discovery function: 'Search AppStack releases' and 'Use this to discover releases before calling get_release_overview'.
Attacks that exploit this kind of access
Search AppStack releases in a Yunxiao organization. Use this to discover releases before calling get_release_overview or other release-specific tools. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
search_releases accepts 9 parameters: sort, states, orderBy, perPage, nextToken, pagination, systemName, nameKeyword, organizationId. 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 search_releases: 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.
search_releases 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 search_releases 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 search_releases. 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.
search_releases 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 →