Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_aireplay

Destructive

Executes aireplay-ng directly with argv tokens in an isolated engagement workspace, avoiding shell parsing and supporting relative paths for engagement artifacts.

Instructions

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

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
Behavior3/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 danger profile is carried by structured data. The description adds genuinely useful behavior: the container invokes aireplay-ng directly with argv tokens and never uses shell parsing, which tells the agent about injection safety and argument handling. It still says nothing about execution time, failures, or limits.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action, then the execution model, then the filesystem/namespace convention. Every sentence adds information an agent needs and there is no boilerplate.

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 safety profile is handled by annotations. For a destructive arbitrary-argv wrapper the definition covers the essential execution model and path conventions, with only stdin behavior and failure modes unstated.

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

Parameters4/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, and it largely does: 'arguments' are defined as argv tokens passed straight to aireplay-ng (no shell parsing), and 'engagement_id' plus 'working_directory' are explained via the engagement namespace and relative-path guidance. Only 'stdin' is left unaddressed.

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?

States a specific verb and resource: run aireplay, and further clarifies the underlying binary is aireplay-ng from the OpenCyber wireless toolkit. An agent can distinguish it from oc_aircrack/oc_airodump by binary name, though the description never explicitly contrasts their roles.

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?

Provides operational context (run from the selected engagement namespace, use relative paths for engagement artifacts) but gives no explicit when-to-use or when-not-to-use guidance versus sibling wireless tools like oc_airmon or oc_airodump. Usage is only implied by the named binary's function.

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