kube_bench_cis
A execute tool on the Intellirecon Console MCP server.
This record as markdown: /tools/intellirecon-console/kube-bench-cis.md
What kube_bench_cis does on Intellirecon Console
AI agents invoke kube_bench_cis 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_bench_cis is rated High
kube-bench executes security compliance checks against a live Kubernetes cluster by querying cluster configuration and running diagnostic commands. This constitutes execution of external operations against infrastructure. Empty description lowers confidence, but the tool name strongly implies active scanning/execution against a Kubernetes environment.
From the tool's definition Tool name 'kube_bench_cis' suggests running kube-bench, a tool that checks Kubernetes clusters against CIS benchmarks. The description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
The rule that runs kube_bench_cis 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_bench_cis, this is the rule to start with:
kube_bench_cis 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_bench_cis call is checked against it from then on.
Questions about kube_bench_cis
kube_bench_cis 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_bench_cis: 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_bench_cis 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_bench_cis 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_bench_cis. 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_bench_cis 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