Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_wfuzz

Destructive

Executes wfuzz web fuzzing commands inside an isolated engagement namespace, letting security teams test web endpoints and save results to engagement artifacts using relative paths.

Instructions

Run wfuzz from the OpenCyber web toolkit. The container executes wfuzz 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_wfuzz"
  }
}

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?

The annotations already disclose that this is not read-only, is open-world, is not idempotent, and is destructive. The description adds useful execution behavior by stating that argv tokens are passed directly without shell parsing and that execution occurs in the engagement namespace, but it does not elaborate on the destructive/open-world implications beyond what annotations provide.

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?

The description is three short, front-loaded sentences. The first sentence establishes the action, the second explains execution semantics, and the third covers namespace/path expectations; none of the wording feels wasted.

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?

The tool has four parameters with no schema descriptions and is annotated as destructive and open-world, so the description should be relatively complete. It covers the core execution model and namespace/path behavior, but leaves `stdin` undocumented and does not add risk or scope guidance beyond the annotations; the existing output schema reduces the need to explain return values.

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 parameter meaning. It explains that `arguments` are supplied argv tokens, ties execution to the selected engagement namespace for `engagement_id`, and indicates relative-path expectations for engagement artifacts, but it never mentions the `stdin` parameter and gives no direct semantic detail for `working_directory`.

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 description states a specific verb and resource: run `wfuzz` from the OpenCyber toolkit, with containerized direct execution rather than shell parsing. It is clear what tool is invoked, but it does not explicitly differentiate this execution path from related tools such as a generic shell or another fuzzing wrapper.

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?

The description gives execution constraints, such as running from the selected engagement namespace and using relative paths for engagement artifacts, but it does not say when to choose `oc_wfuzz` over alternatives. There is no explicit when-to-use, when-not-to-use, or alternative-selection guidance.

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