AI agents call get_pod_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 | Pod name. Use get_kubernetes_object_info to discover valid pod names. |
taskSn | string | — | Optional deployment task serial number for filtering pod info by task. |
namespace | string | Yes | Kubernetes namespace. Use get_kubernetes_object_info to discover valid namespaces. |
resourcePath | string | Yes | Resource proxy path. Typically discovered from application environment resource configurations. |
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 pod metadata and status information from a Kubernetes resource. It performs no side effects, does not execute commands, does not modify state, and does not delete resources. It is a straightforward read operation consistent with inspecting infrastructure state for observability purposes.
From the tool's definition Tool description states 'Get detailed information about a pod' and 'inspect pod status, containers, and events' — purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get detailed information about a pod in an AppStack resource proxy. Use this to inspect pod status, containers, and events. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_pod_info accepts 5 parameters: name, taskSn, namespace, resourcePath, organizationId. Required: name, namespace, resourcePath. 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_pod_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_pod_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_pod_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_pod_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_pod_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 →