k8s_get_services
AI agents call k8s_get_services 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 retrieves Kubernetes Service object metadata and status from the cluster. It enables read-only querying of network service configuration, endpoints, and routing rules—information that could expose internal topology and service locations in a 5G Core environment. The risk is informational disclosure rather than direct system modification.
From the tool's definition Tool name 'k8s_get_services' indicates retrieval of Kubernetes Service resources. The 'get' prefix and context (sibling tools like k8s_get_pods, k8s_get_deployments, k8s_get_nodes) confirm this is a query/list operation with no side effects.
Attacks that exploit this kind of access
k8s_get_services. 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_services: 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_services 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_services 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_services. 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_services 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 →