AI agents call list_systems 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 |
|---|---|---|---|
current | number | — | Page number for pagination. Starts at 1. |
pageSize | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
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 lists existing systems without modifying, deleting, or executing operations. It is purely informational and serves as a navigation/discovery mechanism. The blast radius of misuse is minimal—an attacker could enumerate systems but cannot alter infrastructure or trigger deployments.
From the tool's definition Tool name 'list_systems' and description 'List AppStack systems in a Yunxiao organization' indicate a query/enumeration operation with no side effects. Described as 'entry point to discover systems', which is typical discovery/retrieval behavior.
Attacks that exploit this kind of access
List AppStack systems in a Yunxiao organization. Use this as the entry point to discover systems before calling other system-specific tools. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_systems accepts 3 parameters: current, pageSize, 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_systems: 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_systems 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_systems 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_systems. 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_systems 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 →