AI agents call get_global_var 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 |
|---|---|---|---|
name | string | Yes | Global variable name. Use list_global_vars to discover valid names. |
revisionSha | string | — | Optional revision SHA to retrieve a specific version of the variable. |
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 configuration or state data (global variables) from the Yunxiao DevOps platform without side effects. It is a pure query operation that does not modify, delete, or execute anything. The blast radius if misused is low, as reading global variables typically exposes configuration or non-sensitive metadata at worst.
From the tool's definition Tool description states 'Get an AppStack global variable by name' and instructs to 'Use list_global_vars to discover valid global variable names.' The verb 'Get' and the read-only retrieval pattern indicate no data modification, creation, deletion, or…
Attacks that exploit this kind of access
Get an AppStack global variable by name. Use list_global_vars to discover valid global variable names. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_global_var accepts 3 parameters: name, revisionSha, organizationId. Required: name. 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_global_var: 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_global_var 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_global_var 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_global_var. 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_global_var 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 →