Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_wafw00f

Destructive

Detects and fingerprints Web Application Firewalls by running WAF detection arguments in an isolated engagement workspace without shell parsing.

Instructions

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

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
Behavior4/5

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

Annotations already declare destructive=true, openWorldHint=true and non-idempotent, so the risk profile is covered structurally. The description adds genuinely useful behavior beyond that: arguments are passed as raw argv tokens with no shell parsing, and execution is scoped to the selected engagement namespace with relative paths resolved against it. It stops short of saying what happens on tool failure or whether scans touch the network live, but it clears the bar set by the annotations.

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, execution semantics front-loaded, no filler or restated boilerplate. It is tight, though the small amount of text spent on namespace/paths would have been better spent explaining the tool's purpose.

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 the annotations plus notes cover safety and execution mechanics. What is missing for correct invocation is the core functional description — what wafw00f detects and what a typical argv invocation looks like — which matters for a destructive, open-world scanning tool with four undocumented parameters.

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 carries the burden and partially meets it: 'supplied argv tokens' explains that `arguments` is a passthrough argv list, 'engagement namespace' explains `engagement_id`, and 'relative paths' explains `working_directory`. The `stdin` parameter is never mentioned, and no argv syntax or examples are given, so the compensation is only partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific executable ('Run wafw00f') and the toolkit it belongs to, so the verb+resource pair is concrete. However, it never says what wafw00f actually does (web application firewall fingerprinting), so an agent unfamiliar with the binary gets no functional summary, and it gives no differentiation from the many oc_* siblings it sits beside.

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 only guidance is operational ('Runs from the selected engagement namespace; use relative paths for engagement artifacts'), which tells the agent where files resolve rather than when to pick this tool. There is no statement of when to use this versus oc_bash or other recon wrappers, and no prerequisites such as target reachability or requiring a valid engagement.

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