Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_airmon

Destructive

Run airmon-ng commands with supplied arguments to manage wireless interfaces and monitor mode, using direct execution without shell parsing inside the engagement workspace.

Instructions

Run airmon from the OpenCyber wireless toolkit. The container executes airmon-ng 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_airmon"
  }
}

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, idempotentHint=false, and readOnlyHint=false. The description adds genuinely non-redundant behavior: argv tokens are passed directly with no shell parsing, and execution is scoped to the selected engagement namespace. It does not spell out what destruction means in practice (e.g. that airmon-ng can terminate conflicting processes), which keeps it from a 5.

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, front-loaded with the action and followed by the two facts that matter for safe invocation. Minor redundancy between 'Run airmon' and 'executes `airmon-ng` directly', but nothing is padded.

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 explained. However, for a tool annotated destructiveHint=true and openWorldHint=true with zero schema coverage, the description omits what can be disrupted and gives no example argument shapes, leaving real gaps for an agent composing a wireless-mode change.

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 compensate. It meaningfully covers three of four parameters: `arguments` as raw argv tokens, `working_directory` via relative-path guidance, and `engagement_id` via the namespace statement. `stdin` is not addressed at all, and no argument format examples are given.

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 uses a specific verb+resource: run `airmon-ng` from the wireless toolkit with supplied argv tokens. That distinguishes it well from siblings like oc_aircrack and oc_airodump, which the sibling naming implies are different binaries. It stops short of explicitly contrasting behavior with those siblings, so it lands at 4 rather than 5.

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?

It states an operational constraint (relative paths for engagement artifacts) but gives no when-to-use vs when-not guidance and no alternative tool routing. An agent knows how to invoke it, not when airmon-ng is the right choice over oc_airodump or oc_aireplay.

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