AI agents call list_global_vars 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 |
|---|---|---|---|
search | string | — | Optional search keyword for filtering variable groups by name. |
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 queries and lists configuration data (global variable groups) without creating, modifying, deleting, or executing any operations. It serves as a lookup function to help users identify resources before taking further action. The blast radius is minimal—an AI agent misusing this would at most discover information it shouldn't access, not alter or execute anything. Classified as Read with low severity.
From the tool's definition Tool description explicitly states 'Search AppStack global variable groups' and 'discover variable group IDs' — core read operations with no modification or execution.
Attacks that exploit this kind of access
Search AppStack global variable groups. Use this to discover variable group IDs before reading or updating specific groups. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_global_vars accepts 4 parameters: search, 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_global_vars: 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_global_vars 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_global_vars 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_global_vars. 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_global_vars 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 →