Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_bully

Destructive

Execute bully wireless WPS attack arguments directly in an isolated engagement workspace, with no shell parsing, to run authorized wireless tests.

Instructions

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

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.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the risk profile is known. The description adds genuinely useful behavior beyond that: execution happens without shell parsing, so argument quoting/injection semantics differ from a shell call, and the process is scoped to an engagement namespace. It says nothing about required authorization, target scope, or side effects on the wireless target, which is a gap for a destructive attack tool.

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 primary action, then the execution model, then the namespace/path constraint. Nothing is redundant, though the second and third sentences could be tightened into one.

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 explained, and the description covers the tool's execution model and working-directory convention. What remains missing is how to use `stdin` and what a well-formed argv looks like for this binary, which matters given zero schema description coverage.

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%, so the description must carry the parameter burden, and it only partially does. It clarifies that `arguments` are raw argv tokens passed to `bully` (not a shell string) and that `working_directory` should use relative paths within the engagement namespace, but `engagement_id` and especially `stdin` are never explained, and no example argument patterns are given for a tool whose argv surface is entirely tool-specific.

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 concrete verb and resource: run the `bully` binary from the OpenCyber wireless attack toolkit, and it specifies that argv tokens are passed directly rather than via a shell. It does not explicitly differentiate itself from adjacent wireless siblings such as oc_aircrack or oc_aireplay, but naming the underlying binary makes the scope unambiguous.

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?

Usage is implied rather than stated: an agent can infer it should call this when it needs the `bully` tool specifically, and the note about running from the selected engagement namespace with relative paths is a real operational constraint. However, there is no explicit when-to-use vs when-not guidance and no mention of an alternative such as a generic shell runner for cases where this wrapper is inappropriate.

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