Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_kube_hunter

Destructive

Run Kubernetes exposure scans from a selected engagement workspace, passing arguments directly without shell parsing and writing artifacts to relative paths.

Instructions

Run kube hunter from the OpenCyber cloud container iac toolkit. The container executes kube-hunter 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_hunter"
  }
}

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

B3.2/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false. The description adds useful execution details such as direct argv invocation without shell parsing and engagement-namespace execution, but it does not explain the practical impact of destructive behavior, required permissions, or rate limits.

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?

The description is three focused sentences and front-loads the core action. Each sentence adds useful operational or scoping context with little wasted wording.

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

Completeness3/5

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

Because an output schema exists and annotations already flag the destructive/open-world profile, the description does not need to explain return values or safety warnings in depth. However, for a destructive external scanning tool with four parameters and 0% schema coverage, the lack of stdin documentation and usage guidance leaves meaningful gaps.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies that arguments are supplied as argv tokens without shell parsing, that execution uses the engagement namespace, and that relative paths should be used, but it does not mention stdin and only indirectly addresses working_directory.

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 states a specific verb and resource: run kube-hunter from the OpenCyber toolkit. It clearly conveys the tool's action, though it does not explicitly differentiate it from siblings such as oc_kube_bench.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no exclusions, and no usage scenarios. The description only gives operational constraints about execution context and paths.

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