AI agents call get_deploy_group 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 |
|---|---|---|---|
poolName | string | Yes | Resource pool name. Typically discovered from application environment details. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
deployGroupName | string | Yes | Deploy group name. Typically discovered from deployment configuration. |
Parameters from the server's own tool schema.
This tool retrieves information about a deploy group (a configuration object defining machine subsets) by name from the Yunxiao DevOps platform. It has no side effects, does not execute deployments, does not modify state, and does not delete resources. It is purely a data retrieval operation, characteristic of the Read category.
From the tool's definition Tool description states 'Get an AppStack deploy group by name' — a retrieval operation with no modification, deletion, or execution capability. The verb 'Get' and the read-only nature of querying deploy group metadata indicate a query operation.
Attacks that exploit this kind of access
Get an AppStack deploy group by name within a resource pool. Deploy groups define subsets of machines for targeted deployments. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_deploy_group accepts 3 parameters: poolName, organizationId, deployGroupName. Required: poolName, deployGroupName. 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_deploy_group: 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_deploy_group 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_deploy_group 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_deploy_group. 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_deploy_group 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 →