AI agents call get_pod_container_log 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. |
container | string | Yes | Container name within the pod. Typically discovered from pod info. |
namespace | string | Yes | Kubernetes namespace. Use get_pod_info or get_kubernetes_object_info to discover valid namespaces. |
resourcePath | string | Yes | Resource proxy path. Typically discovered from application environment resource configurations. |
tailingLines | number | — | Number of recent log lines to return. Defaults to 1000. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
The tool retrieves diagnostic logs for debugging purposes. It does not execute commands, modify infrastructure, delete data, or trigger deployments. The blast radius of misuse is minimal — an attacker would gain visibility into application logs (which may contain sensitive information, justifying 'low' rather than negligible severity) but cannot alter state or compromise availability. This is a pure Read operation.
From the tool's definition Tool description states 'Get container logs from a pod' and 'retrieve recent logs' — these are query/retrieval operations with no modification or execution of workloads.
Attacks that exploit this kind of access
Get container logs from a pod in an AppStack resource proxy. Use this to retrieve recent logs for debugging deployment issues. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_pod_container_log accepts 6 parameters: name, container, namespace, resourcePath, tailingLines, organizationId. Required: name, container, 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_container_log: 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_container_log 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_container_log 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_container_log. 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_container_log 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 →