Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_iw

Destructive

Inspect and configure Linux wireless interfaces, including enabling monitor mode, from an engagement namespace. Use it to view PHY details, set interface modes, and manage wireless state during authorized security testing.

Instructions

Inspect and configure Linux wireless interfaces, including monitor mode. Requires a wireless PHY inside the container and CAP_NET_ADMIN. 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_iw"
  }
}

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.1/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 risk profile is partly covered. The description adds real value beyond them by naming the CAP_NET_ADMIN and PHY requirements and the engagement-namespace/path constraint, but it never says what a destructive invocation can tear down (existing interface modes, monitor-mode state) or that failures occur when no PHY is mapped in.

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 capability and then the environment constraints; no filler. Minor loss for packing three distinct concerns (capability, kernel/cap requirements, pathing) without visual separation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 destructive raw-CLI passthrough with zero schema coverage, the description omits the single most important calling detail: that 'arguments' is the verbatim iw argument vector, ideally with an example subcommand. Given the destructive annotation and untyped argv, that omission is a meaningful gap.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 4 parameters, so the description must carry the burden. It only hints at working_directory ('use relative paths for engagement artifacts') and never explains that 'arguments' is a raw argv array for the underlying iw binary, nor what 'stdin' or 'engagement_id' mean in this context.

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 pair ('Inspect and configure') and a concrete resource ('Linux wireless interfaces'), with monitor mode called out as a notable capability. It does not differentiate itself from nearby wireless siblings such as oc_airmon or oc_airodump, so it stops short of a 5.

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?

The description supplies prerequisites (wireless PHY present in the container, CAP_NET_ADMIN) which is genuinely useful usage context, but it never says when to prefer this over the airmon/airodump/aireplay siblings or when it is unsuitable. Guidance is implied rather than explicit.

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