AI agents call list_environments 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 |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
sort | string | — | Sort direction. Valid values: asc, desc. |
appName | string | Yes | Application name. Use list_applications to discover valid names. |
orderBy | string | — | Sort field. Valid values: id, gmtCreate. |
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. |
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 displays existing environment configurations for an application without creating, modifying, or deleting any data. It is a purely informational query operation typical of DevOps platforms used for discovery and inspection. The low severity reflects minimal blast radius—listing environments cannot harm infrastructure or data.
From the tool's definition Tool name 'list_environments' and description 'List AppStack environments for an application' indicate a retrieval operation with no side effects. The verb 'list' and the stated purpose of discovering/querying environments confirm this is a read-only query.
Attacks that exploit this kind of access
List AppStack environments for an application. Use list_applications to discover valid application names. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_environments accepts 8 parameters: page, sort, appName, orderBy, perPage, nextToken, pagination, 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_environments: 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_environments 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_environments 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_environments. 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_environments 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 →