AI agents call list_resource_instances 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. |
poolName | string | Yes | Resource pool name. Typically found in application environment resource configurations. |
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 performs a read-only listing operation to query resource instances from a resource pool. It retrieves information without creating, modifying, deleting, or executing any operations. The action is informational and non-destructive, fitting squarely within the Read category with low severity due to minimal blast radius from misuse.
From the tool's definition Tool name 'list_resource_instances' and description 'List AppStack resource instances in a resource pool' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
List AppStack resource instances in a resource pool. Pool names are typically found in application environment resource configurations. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_resource_instances accepts 8 parameters: page, sort, orderBy, perPage, poolName, nextToken, pagination, organizationId. Required: poolName. 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_resource_instances: 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_resource_instances 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_resource_instances 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_resource_instances. 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_resource_instances 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 →