Analyze service endpoints and connectivity
AI agents call analyze_service_connectivity 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 queries Kubernetes service state and network configuration to provide diagnostics. It does not create, modify, delete, or execute arbitrary operations—it retrieves and interprets existing cluster metadata. The sibling tools (check_pod_status, cluster_health_check, get_pod_logs) confirm the pattern of observability-focused Read operations.
From the tool's definition Tool name 'analyze_service_connectivity' and description 'Analyze service endpoints and connectivity' indicate observation and diagnostic operations without modification.
Attacks that exploit this kind of access
Analyze service endpoints and connectivity. 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 analyze_service_connectivity: 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.
analyze_service_connectivity 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 analyze_service_connectivity 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 analyze_service_connectivity. 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.
analyze_service_connectivity is provided by the Kubernetes MCP Server MCP server (vivekbala/mcp). 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 →