Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_dotdotpwn

Destructive

Executes directory traversal and file inclusion scans through the OpenCyber web toolkit, passing supplied arguments directly and using engagement-scoped working directories.

Instructions

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

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/5.0
Behavior3/5

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

Annotations already declare destructive=true, openWorldHint=true, and readOnly=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: argv tokens are executed directly with no shell parsing (so shell metacharacters are not interpreted) and execution happens inside the selected engagement namespace. It does not explain what the destructive impact of running the fuzzer could be or how its output is surfaced.

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 identity of the wrapped binary, with no filler. Each sentence carries information, though the phrase about the OpenCyber web toolkit is near-redundant with the tool's 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?

The presence of an output schema and rich annotations reduces what the description must cover, and the argv/no-shell detail is a helpful addition. Still, for a destructive, open-world fuzzer with four zero-documented parameters, the definition leaves the agent without knowledge of what the tool scans for, what typical arguments look like, or what `stdin` is for.

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

Parameters2/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 full burden. It clarifies that `arguments` is an argv token list with no shell interpretation and hints that `working_directory` should use relative paths, but `engagement_id` is only loosely gestured at ('selected engagement namespace') and `stdin` is never mentioned at all.

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 the `dotdotpwn` binary) and makes clear it is the toolkit's wrapper for that executable. It does not, however, say what dotdotpwn actually accomplishes (directory-traversal fuzzing), so an agent unfamiliar with the binary must infer the purpose from the name alone; there is also no explicit differentiation from siblings like oc_bash or oc_api_fuzz.

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 no statement of when to choose this tool versus oc_bash or other fuzzing wrappers, and no preconditions or exclusions are given. The only usage-adjacent instruction is 'use relative paths for engagement artifacts', which addresses the working directory rather than tool selection.

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