Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_dirb

Destructive

Executes dirb with explicit argument tokens in an isolated engagement namespace to enumerate web server content paths without shell parsing.

Instructions

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

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

A3.8/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 behavior: execution is direct argv with no shell parsing (so quoting/metacharacters are not interpreted), and the process runs inside the selected engagement namespace with a default working directory of '.', which tells the agent where output artifacts land.

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?

Three short sentences, front-loaded with what it is and the execution model before the path guidance. Every clause carries information an agent would otherwise have to guess, and there is no repetition of the schema or annotations.

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?

Because an output schema exists, return values need not be described, and the destructive/open-world behavior is covered by annotations. Still, for a tool that accepts arbitrary argv against a remote target, the description says nothing about what dirb does, expected argument forms, or when the run is long-lived or rate-limited, leaving meaningful gaps for an agent invoking it cold.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load, and it does for three of four parameters: `arguments` is characterized as raw argv tokens passed straight to the binary, `working_directory` is framed by the relative-path-for-artifacts rule, and `engagement_id` is tied to the selected engagement namespace. Only `stdin` goes unmentioned, which keeps it below a 5.

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: it runs `dirb` from the OpenCyber web toolkit, which tells an agent this is the dirb wrapper rather than a generic shell or an unrelated scanner. It does not, however, compare itself to any sibling (e.g. oc_bash or other web fuzzers), leaving the differentiation implicit in the tool name alone.

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?

The definition gives operational context – pass argv tokens, run against an engagement namespace, use relative paths for artifacts – which implies how and where to call it. It never states when to prefer this over oc_bash or other content-discovery tools, and gives no when-not guidance or prerequisites for the 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