AI agents call get_env_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. |
envName | string | Yes | Environment name. Use list_environments to discover valid environment 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 environment-specific configuration variables, which is a read-only operation with no side effects. It fetches data (variable groups) for informational purposes. The blast radius is low as misuse would only expose configuration details rather than modify, delete, or execute operations. The 'get' prefix and verb 'Get' in the description confirm read semantics.
From the tool's definition Tool name 'get_env_variable_groups' and description 'Get AppStack variable groups for a specific environment' indicate a retrieval operation that queries configuration data without modification.
Attacks that exploit this kind of access
Get AppStack variable groups for a specific environment. Variable groups define environment-specific configuration values. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_env_variable_groups accepts 3 parameters: appName, envName, organizationId. Required: appName, envName. 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_env_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_env_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_env_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_env_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_env_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 →