AI agents call list_applications 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. |
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 is fundamentally a query/list operation (Read category). Severity is medium rather than low because the returned data likely includes deployment topology, infrastructure details, and release pipeline information that could inform reconnaissance for further attacks in a DevOps environment. Confidence is high because the description explicitly states 'list' and references a read-only organizational inventory.
From the tool's definition Tool name and description indicate it 'List[s] AppStack applications' — a retrieval operation with no side effects. AppStack is a deployment/release platform, so applications are metadata about deployed services.
Attacks that exploit this kind of access
List AppStack applications in a Yunxiao organization. AppStack manages deployment environments and release pipelines. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_applications accepts 7 parameters: page, sort, orderBy, perPage, nextToken, pagination, 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 list_applications: 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_applications 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_applications 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_applications. 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_applications 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 →