Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_gau

Destructive

Runs gau URL discovery against engagement targets using supplied argv arguments without shell parsing, keeping output and relative artifact paths scoped to the selected engagement workspace.

Instructions

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

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false. The description adds genuinely non-obvious behavior beyond those flags: execution is argv-based with no shell interpretation, and it operates within the selected engagement namespace. It does not explain why the tool is destructive or what external services it contacts, so the annotation-driven risk profile stays unexplained.

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?

Two compact sentences, front-loaded with what the tool does and the execution model before the scoping note. Every clause carries information; nothing is padding, though the phrasing is dense enough that the path guidance sits slightly buried at the end.

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. However, for a destructive, open-world tool with a fully undocumented schema, the description should also say what gau yields, what stdin does, and what makes the call destructive; those gaps leave an agent under-informed before invoking it.

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?

With 0% schema description coverage the description must carry the load, and it does for most parameters: `arguments` is defined as literal argv tokens with no shell parsing (so quoting, pipes and redirects will not work), `working_directory` is scoped to relative engagement paths, and `engagement_id` selects the namespace. Only `stdin` is left entirely unexplained.

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?

States a specific action and resource: it runs the `gau` binary inside the OpenCyber toolkit container, and it clarifies the execution model (direct argv execution, no shell). It never explains what `gau` actually produces (URL discovery), so an agent unfamiliar with the binary must infer the purpose from the name, but the operation itself is unambiguous.

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 reach for this tool versus alternatives, and no prerequisites such as whether external network access or API keys are needed. The only directive, 'use relative paths for engagement artifacts', is operational advice rather than selection guidance.

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