Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_feroxbuster

Destructive

Run web content and directory discovery scans with direct argv execution and no shell parsing, scoped to a selected engagement workspace for authorized testing.

Instructions

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

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, and non-idempotent, so the safety profile is covered. The description adds genuinely new context: execution is direct argv with no shell parsing (a safety/injection property), and the process runs scoped to the selected engagement namespace with relative-path artifacts.

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 core action and then the execution constraint. No wasted filler, though the working-directory note could be folded into the argv sentence.

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 described, and the execution model is explained. However, for a raw-argv passthrough tool the description gives no example argument shape, no note on how output is captured, and leaves the stdin parameter entirely undocumented.

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 maps 'arguments' to argv tokens, 'engagement_id' to the engagement namespace, and 'working_directory' implicitly via the relative-paths note, but 'stdin' is never mentioned and no expected argument format or example is given.

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 names a specific verb and resource (run feroxbuster) and explains the execution model (direct argv tokens, no shell). It does not explain what feroxbuster is used for or distinguish this tool from the many other offensive-security siblings, so an agent must already know the tool's role.

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 one practical instruction — use relative paths for engagement artifacts — but no guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions. The agent is left to infer applicability from the tool name alone.

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