Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_kube_bench

Destructive

Executes Kubernetes CIS benchmark checks in the selected engagement namespace using raw argv tokens, without shell parsing, to assess cluster security.

Instructions

Run kube bench from the OpenCyber cloud container iac toolkit. The container executes kube-bench directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_kube_bench"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructive/non-idempotent/openWorld, so the bar is lower, but the description adds genuinely new behavior: argv tokens are passed directly to `kube-bench` with no shell parsing, which tells the agent that quoting and metacharacters are not interpreted. It also discloses the working namespace and path convention. It does not explain the implications of the destructiveHint=true annotation or what state could be affected, which would have completed the picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the binary, with the safety-relevant 'shell parsing is never used' clause placed prominently. The 'OpenCyber cloud container iac toolkit' branding is the only slightly expendable wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the description covers the non-obvious aspects of an argv-passthrough executor: no shell, relative paths, engagement namespace. What is missing is minor but real: stdin handling, expected argument shapes for kube-bench, and any note on what the destructive annotation means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It usefully explains that `arguments` are raw argv tokens (not a shell string) and that `working_directory` should be relative to the engagement namespace, covering two of four parameters. `stdin` and the semantics/validation of `engagement_id` remain undocumented in both the schema and the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and tool ('Run kube bench') and identifies the underlying binary (`kube-bench`) executed in a container, so an agent knows exactly what will run. It does not explicitly contrast itself with close siblings such as oc_docker_bench (different benchmark target) or oc_kube_hunter (different Kubernetes posture tool), leaving that distinction implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the execution context ('runs from the selected engagement namespace') and a usage rule ('use relative paths for engagement artifacts'), which gives real guidance on how to call it. However, there is no explicit when-to-use versus when-not, and no mention of prerequisites such as an existing engagement or target cluster access.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools