AI agents call get_deployment_revision_info 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 | Deployment name. Use get_kubernetes_object_info with kind=Deployment to discover valid deployment names. |
taskSn | string | — | Optional deployment task serial number for filtering revision info by task. |
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. |
revision | string | Yes | Deployment revision number. Use Kubernetes rollout history to discover valid revision numbers. |
namespace | string | Yes | Kubernetes namespace. Use get_application_overview or get_environment_overview to discover valid namespaces. |
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 and queries deployment revision metadata without side effects. It enables inspection of deployment history but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an attacker could gain visibility into deployment timelines and configurations but cannot alter deployments or trigger new rollouts.
From the tool's definition Tool description states 'Get revision information' and 'inspect the rollout history and revision details' — purely informational operations with no modification or execution of infrastructure changes.
Attacks that exploit this kind of access
Get revision information for an AppStack deployment. Use this to inspect the rollout history and revision details of a deployment. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_deployment_revision_info accepts 7 parameters: name, taskSn, appName, envName, revision, namespace, organizationId. Required: name, appName, envName, revision, namespace. 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_deployment_revision_info: 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_deployment_revision_info 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_deployment_revision_info 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_deployment_revision_info. 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_deployment_revision_info 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 →