Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ffuf

Destructive

Run ffuf web fuzzing with explicit argument tokens and no shell parsing, scoped to an engagement namespace with relative artifact paths for authorized security testing.

Instructions

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

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 destructiveHint=true, openWorldHint=true, idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: argv tokens are passed directly with no shell parsing, and execution is scoped to the engagement namespace with relative paths. It omits what happens on failure, timeouts, or how output artifacts are produced.

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 every clause carries information. The only mild waste is the vendor framing ('from the OpenCyber web toolkit'), which adds little for an agent that already resolved the tool name.

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 destructive/open-world nature. However, with zero schema description coverage and four parameters, the description leaves `stdin` and `engagement_id` unexplained and gives no notion of what ffuf actually does for an agent unfamiliar with the binary.

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 clarifies the key `arguments` parameter (argv token list, no shell parsing) and implicitly the `working_directory` semantics (relative to the engagement namespace), but says nothing about `stdin` or `engagement_id`.

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?

Names a specific verb and resource ('Run ffuf') and adds the mechanism ('container executes `ffuf` directly with the supplied argv tokens'), so the agent knows exactly what happens. It does not differentiate itself from sibling fuzzing/execution tools such as oc_api_fuzz or oc_bash, which keeps it from 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage-shaped guidance is operational ('runs from the selected engagement namespace; use relative paths for engagement artifacts'), which is about path resolution rather than tool selection. There is no statement of when to choose this over the many other execution/fuzzing siblings, and no exclusions or prerequisites.

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