Get service dependencies and relationships
AI agents call get_service_dependencies to retrieve information from Kubernetes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Kubernetes service dependencies and relationships without modifying, deleting, or executing any resources. It is a pure read operation that queries existing cluster state. The low severity reflects minimal blast radius—even if misused, it only exposes visibility into service topology without enabling harmful actions.
From the tool's definition Tool name contains 'get' and description explicitly states it 'Get service dependencies and relationships' with no modification verbs (create, delete, update) or execution keywords (run, execute)
Attacks that exploit this kind of access
Get service dependencies and relationships. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for get_service_dependencies: 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. Nothing to install.
get_service_dependencies 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_service_dependencies 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_service_dependencies. 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_service_dependencies is provided by the Kubernetes MCP Server MCP server (surukanti/k8s-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 →