run_k8scan

What run_k8scan does on Pentester-MCP

AI agents invoke run_k8scan to trigger actions in Pentester-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why run_k8scan is rated High

Despite empty tool description, the context strongly indicates this tool executes a reconnaissance/scanning operation against Kubernetes infrastructure. Kubernetes scanning has Execute-level severity because it triggers active network probes and may enumerate or interact with cluster components in ways that depend on the target environment and could cause unexpected side effects.

From the tool's definition Tool name 'run_k8scan' combined with server description stating the server 'autonomously execute[s] over 200 open-source penetration testing tools' including 'reconnaissance, web exploitation, and brute-forcing.' k8scan is a Kubernetes reconnaissance tool…

The rule that runs run_k8scan safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_k8scan": {
      "limits": [
        {
          "counter": "run_k8scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about run_k8scan