check_kubernetes_api

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-kubernetes-api.md

WHAT IT DOES

What check_kubernetes_api does on Mcp Nettools

AI agents call check_kubernetes_api to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_kubernetes_api is rated Low

The tool only retrieves health and version information from Kubernetes API endpoints without making any changes. However, severity is elevated to medium because: (1) it requires network access to a Kubernetes control plane endpoint, (2) reconnaissance of Kubernetes infrastructure could enable further attacks, and (3) misuse could allow mapping of internal Kubernetes clusters.

From the tool's definition Tool description states it 'Check[s] Kubernetes API server health via the /healthz and /version endpoints.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_kubernetes_api safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_kubernetes_api, this is the rule to start with:

check_kubernetes_api Allowed

check_kubernetes_api is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_kubernetes_api": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_kubernetes_api call is checked against it from then on.

FAQ

Questions about check_kubernetes_api

What does the check_kubernetes_api tool do? +

Check Kubernetes API server health via the /healthz and /version endpoints. Returns API server liveness, individual health check details, and Kubernetes version. host: IP or hostname. port: default 6443. https: use HTTPS (default True). It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_kubernetes_api? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_kubernetes_api: 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 Mcp Nettools. Nothing to install.

What risk level is check_kubernetes_api? +

check_kubernetes_api is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_kubernetes_api? +

Yes. Add a rate_limit block to the check_kubernetes_api 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.

How do I block check_kubernetes_api completely? +

Set action: deny in the PolicyLayer policy for check_kubernetes_api. 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.

What MCP server provides check_kubernetes_api? +

check_kubernetes_api is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →