kube_hunter_scan
A execute tool on the Intellirecon Console MCP server.
This record as markdown: /tools/intellirecon-console/kube-hunter-scan.md
What kube_hunter_scan does on Intellirecon Console
AI agents invoke kube_hunter_scan to trigger actions in Intellirecon Console. 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 kube_hunter_scan is rated High
Kube-hunter is a well-known Kubernetes penetration testing/vulnerability hunting tool that actively probes cluster infrastructure. Running such a scan constitutes executing an external security operation with potentially significant blast radius — it could trigger alerts, expose cluster weaknesses, or be used in an attack chain.
From the tool's definition Tool name 'kube_hunter_scan' suggests execution of the kube-hunter security scanning tool against Kubernetes clusters; description is empty and uninformative, lowering confidence
Attacks that exploit this kind of access
The rule that runs kube_hunter_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Intellirecon Console, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kube_hunter_scan, this is the rule to start with:
kube_hunter_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Intellirecon Console, apply this rule, and every kube_hunter_scan call is checked against it from then on.
Questions about kube_hunter_scan
kube_hunter_scan is a execute tool on the Intellirecon Console MCP server. It is categorised as a Execute tool in the Intellirecon Console MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Intellirecon Console MCP server in PolicyLayer and add a rule for kube_hunter_scan: 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 Intellirecon Console. Nothing to install.
kube_hunter_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kube_hunter_scan 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 kube_hunter_scan. 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.
kube_hunter_scan is provided by the Intellirecon Console MCP server (dokotela021/intellirecon-console). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Intellirecon Console, and thousands of servers like it.
Across the catalogue