AI agents call get_app_variable_groups 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 |
|---|---|---|---|
appName | string | Yes | Application name. Use list_applications to discover valid app names. |
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 metadata about variable groups without side effects. It is a read-only discovery operation that returns information to help users identify available resources, analogous to a list or get operation. The low severity reflects minimal blast radius — exposing variable group names does not directly compromise systems or data, though it may inform reconnaissance.
From the tool's definition Tool description states 'List AppStack variable groups for an application' and 'discover variable group names' — pure discovery/enumeration with no modification, deletion, or execution.
Attacks that exploit this kind of access
List AppStack variable groups for an application. Use this to discover variable group names before reading specific groups. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_app_variable_groups accepts 2 parameters: appName, 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 get_app_variable_groups: 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.
get_app_variable_groups 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 get_app_variable_groups 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 get_app_variable_groups. 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.
get_app_variable_groups 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 →