Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_reaver

Destructive

Runs Reaver commands with supplied argument tokens to test WPS-enabled wireless access points, executing directly without shell parsing inside an engagement workspace.

Instructions

Run reaver from the OpenCyber wireless attack toolkit. The container executes reaver 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_reaver"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the binary is invoked directly with argv tokens and shell parsing is never used, which tells the agent how to construct arguments safely, plus the engagement-namespace scoping of the working directory.

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 tight sentences with no filler, and the most important facts (what runs, and the no-shell-parsing execution model) are front-loaded. Nothing is wasted, though it could be organized a bit more crisply around parameter guidance.

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?

An output schema exists, so return values need not be described, and annotations cover the risk profile. However, with four parameters at 0% schema coverage and no explanation of stdin or of when this tool is the right choice, the definition leaves meaningful gaps for an agent deciding whether and how to call it.

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 carries the burden. It sheds light on 'arguments' as raw argv tokens and on 'working_directory' via the relative-path instruction, and hints at 'engagement_id' through the engagement-namespace sentence, but 'stdin' is left entirely undefined in both schema and 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 states a specific verb and resource: 'Run reaver from the OpenCyber wireless attack toolkit', and clarifies the execution model (direct argv execution, no shell parsing). It is clear what the tool does, though it does not explicitly contrast itself with wireless siblings such as oc_aircrack or oc_airmon.

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?

The only usage guidance is operational ('Runs from the selected engagement namespace; use relative paths for engagement artifacts'). There is no guidance on when to choose reaver over the other wireless tools, no mention of prerequisites such as a monitor-mode interface, and no exclusions.

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