Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_mdk4

Destructive

Execute mdk4 wireless attack commands with direct argv tokens inside an engagement namespace, supporting authorized Wi-Fi testing with relative artifact paths.

Instructions

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

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 non-obvious behavior beyond that: argv tokens are passed directly with no shell parsing (so no shell metacharacters, quoting, or pipes work), and execution is scoped to the engagement namespace. It stops short of describing what mdk4 output or failure modes look like, but the added execution-model detail is genuinely useful.

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 short sentences, front-loaded with purpose and immediately followed by the most agent-relevant constraint (no shell parsing). No filler or restatement of the title; only the final clause about relative paths is slightly compressed.

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 no explanation. However, for a destructive, zero-schema-coverage tool the description should say more about how to format mdk4 arguments (e.g. that flags must be separate tokens), what stdin is for, and any preconditions like an interface in monitor mode. The execution model is well covered; the invocation prerequisites are not.

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 the load. It does clarify that 'arguments' are raw argv tokens (not a shell string), that execution is rooted in the engagement namespace (engagement_id), and that artifact paths should be relative (working_directory). The 'stdin' parameter is never mentioned, leaving one of four parameters undocumented in any field.

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 first sentence states a specific verb and resource ('Run mdk4 from the OpenCyber wireless attack toolkit'), so the agent knows exactly what will execute. It does not differentiate from sibling wireless tools such as oc_aircrack, oc_aireplay, or oc_airmon, leaving tool selection to the agent's own knowledge of mdk4.

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 choose mdk4 over the many sibling wireless tools, nor any stated preconditions (monitor mode interface, root privileges, target scope). The only guidance is operational ('use relative paths for engagement artifacts'), which tells the agent how to pass paths but not when this tool is the right choice.

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