Given an application name, retrieves the status of the pods
AI agents call k8s.app_status to retrieve information from K8s Mcp Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a pure data retrieval operation with no side effects. It queries the status of existing pods in a Kubernetes cluster but does not create, modify, delete, or execute any operations. The read-only nature of the server and the passive inspection intent of the tool place it squarely in the Read category.
From the tool's definition Tool retrieves pod status given an application name. Server description explicitly states 'read-only' and lists operations like 'inspect app status, view pod events, and fetch container logs' without any modification capabilities.
Attacks that exploit this kind of access
Given an application name, retrieves the status of the pods. It is categorised as a Read tool in the K8s Mcp Assistant MCP Server, which means it retrieves data without modifying state.
Register the K8s Mcp Assistant MCP server in PolicyLayer and add a rule for k8s.app_status: 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 K8s Mcp Assistant. Nothing to install.
k8s.app_status 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 k8s.app_status 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 k8s.app_status. 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.
k8s.app_status is provided by the K8s Mcp Assistant MCP server (nicolasmosquerar/k8s-mcp-assistant). 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 →