AI agents call get_kubernetes_object_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 |
|---|---|---|---|
kind | string | Yes | Kubernetes object kind. Valid values: Pod, Deployment, Service, ConfigMap, Secret, Ingress, StatefulSet, DaemonSet, etc. |
name | string | Yes | Kubernetes object name. Use Kubernetes conventions to identify objects by name. |
taskSn | string | — | Optional deployment task serial number for filtering object info by task. |
namespace | string | Yes | Kubernetes namespace. Use get_application_overview or get_environment_overview 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 Kubernetes object information (pods, deployments, services) without any side effects. It is a passive information-gathering operation typical of monitoring and introspection use cases in DevOps platforms. No data is created, modified, deleted, or executed.
From the tool's definition Tool name includes 'get_' prefix; description states 'Get detailed information' with no modification, deletion, or execution capability mentioned. Scope is read-only retrieval of Kubernetes object metadata and status.
Attacks that exploit this kind of access
Get detailed information about a Kubernetes object in an AppStack resource proxy. Supports pods, deployments, services, and other Kubernetes resources. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_kubernetes_object_info accepts 6 parameters: kind, name, taskSn, namespace, resourcePath, organizationId. Required: kind, 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_kubernetes_object_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_kubernetes_object_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_kubernetes_object_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_kubernetes_object_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_kubernetes_object_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 →