start_k8scan_server

What start_k8scan_server does on Pentester-MCP

AI agents invoke start_k8scan_server 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 start_k8scan_server is rated High

This tool executes and launches a scanning infrastructure component (k8scan is a Kubernetes security scanner). While not destructive by itself, it triggers autonomous reconnaissance/scanning operations whose scope and impact depend on how the server is configured and what network it targets. This aligns with Execute category—it runs tools/processes whose effects depend on arguments and execution context.

From the tool's definition Tool name 'start_k8scan_server' indicates initiation of a Kubernetes security scanning server. The parent server description explicitly states it 'enables AI assistants to autonomously execute over 200 open-source penetration testing tools' including 'web…

The rule that runs start_k8scan_server 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 start_k8scan_server, this is the rule to start with:

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

Questions about start_k8scan_server