k8s_get_deployments
AI agents call k8s_get_deployments to retrieve information from Kubernetes MCP Server – 5G Core Edition without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Kubernetes deployment objects and returns their state/configuration. It has no side effects—it only retrieves data about running deployments. Although the description is empty, the naming pattern and context as part of a cluster state inspection API strongly indicate a Read operation.
From the tool's definition Tool name 'k8s_get_deployments' follows Kubernetes API naming convention for retrieval operations (get). Sibling tools like k8s_describe_pod, k8s_get_configmaps, k8s_get_events, k8s_get_nodes, k8s_get_pod_logs, and k8s_get_pods establish a pattern of…
Attacks that exploit this kind of access
k8s_get_deployments. It is categorised as a Read tool in the Kubernetes MCP Server – 5G Core Edition MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server – 5G Core Edition MCP server in PolicyLayer and add a rule for k8s_get_deployments: 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 Kubernetes MCP Server – 5G Core Edition. Nothing to install.
k8s_get_deployments 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_get_deployments 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_get_deployments. 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_get_deployments is provided by the Kubernetes MCP Server – 5G Core Edition MCP server (sanzco/mcp5g). 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 →