Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_aircrack

Destructive

Runs aircrack-ng with supplied argument tokens inside an engagement workspace for authorized wireless security testing, without shell parsing; use relative paths for engagement artifacts.

Instructions

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

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 declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=false, so the risk profile is largely covered. The description does add genuinely useful behavior beyond that: argv tokens are executed directly with no shell parsing, which tells the agent there is no injection risk and that arguments must be pre-split. It still does not describe what output or side effects result from a destructive run.

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 the core action front-loaded and no filler. The execution-mechanics sentence and the path-scoping sentence each add distinct information, though the phrasing could be trimmed slightly.

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, and for a thin CLI wrapper the description covers the essentials. However, with 0% schema coverage it should at minimum mention that `stdin` accepts piped input and clarify what argument syntax is expected (e.g., raw aircrack-ng flags).

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, and it partially does: 'supplied argv tokens' maps to `arguments`, 'selected engagement namespace' to `engagement_id`, and 'use relative paths for engagement artifacts' to `working_directory`. The `stdin` parameter is never mentioned, leaving one of four parameters undocumented anywhere.

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 resource: it runs `aircrack-ng` from the OpenCyber wireless toolkit, which is clearly a distinct binary from siblings like oc_airmon or oc_airodump. It stops short of explicitly contrasting its role with those related wireless tools, so the agent must infer the division of labor from the binary name alone.

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 statement of when to use this tool versus the other wireless siblings, no preconditions (e.g., monitor mode required, capture file needed), and no exclusions. The only operational hint is that engagement-relative paths should be used, which is a constraint rather than usage guidance.

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