Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_pixiewps

Destructive

Run WPS Pixie Dust attack computations with supplied argv tokens in an engagement workspace to recover wireless credentials from captured handshake data.

Instructions

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

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 destructive=true, openWorld=true, readOnly=false, idempotent=false, so the safety profile is covered. The description adds genuinely new behavioral context: argv tokens are passed directly to `pixiewps` with no shell parsing, and execution is scoped to the selected engagement namespace. It stops short of describing failure modes or output characteristics, but that gap is partly offset by the output schema.

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 the action and followed by the two execution semantics that matter most (no shell parsing, namespace scoping). No filler; the only weakness is that no line is spent on the parameter names the schema leaves bare.

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 annotations cover the safety profile. However, for a destructive, open-world binary wrapper with zero schema documentation, the description leaves `stdin` unexplained and gives no hint about expected argv structure or typical invocation, which an agent would need to call this correctly.

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 clarifies `arguments` as raw argv tokens (not a shell string), ties `working_directory` to relative engagement-artifact paths, and ties `engagement_id` to the namespace, but it never mentions the `stdin` parameter or gives argument format/examples for pixiewps flags, leaving one of four parameters wholly undocumented.

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 the `pixiewps` binary from the OpenCyber wireless toolkit. The binary name alone distinguishes it from the many sibling wrappers (oc_aircrack, oc_aireplay, etc.), but the description never explains what pixiewps is for or contrasts it with those siblings, leaving the agent to rely on outside domain knowledge.

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 operational how-to ('use relative paths for engagement artifacts') but no when-to-use guidance, no prerequisites, and no named alternatives. An agent cannot tell from the text whether this belongs in a WPS attack chain or when to prefer a sibling tool.

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