List pods in a cluster, optionally scoped to a namespace.
AI agents call list_pods to retrieve information from Rancher MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about pods without creating, modifying, deleting, or executing anything. It is a read-only listing operation consistent with other read-category tools on the server (list_clusters, list_namespaces, list_deployments, list_nodes, list_catalog_apps).
From the tool's definition Tool name is 'list_pods' and description states it 'List pods in a cluster, optionally scoped to a namespace' — a pure retrieval operation with no data modification or execution capability.
Attacks that exploit this kind of access
List pods in a cluster, optionally scoped to a namespace. It is categorised as a Read tool in the Rancher MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rancher MCP Server MCP server in PolicyLayer and add a rule for list_pods: 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 Rancher MCP Server. Nothing to install.
list_pods 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 list_pods 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 list_pods. 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.
list_pods is provided by the Rancher MCP Server MCP server (lokimcpuniverse/rancher-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 →