Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_fierce

Destructive

Run fierce DNS and network enumeration inside an isolated engagement workspace, passing arguments directly without shell parsing to map hosts and subdomains.

Instructions

Run fierce from the OpenCyber enumeration toolkit. The container executes fierce 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_fierce"
  }
}

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, openWorldHint=true, and non-idempotent, so the safety profile is covered. The description adds real behavioral context beyond that: the container invokes the binary directly with argv tokens and never uses shell parsing, which tells the agent quoting/injection concerns do not apply, plus the namespace and working-directory model. It omits output/error behavior, but the output schema covers returns.

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, then the execution model, then the path convention. No filler or restatement of the tool name. It could be tightened slightly, but every sentence contributes a distinct fact.

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?

Annotations cover the destructive/open-world profile and an output schema covers returns, so the description's burden is lighter. It adequately explains the execution and path model for a 4-parameter tool, but leaves the undocumented `stdin` parameter and the tool's actual enumeration purpose unaddressed.

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 the load. It clarifies that `arguments` is a verbatim argv token list, that `engagement_id` selects the namespace, and that `working_directory` should hold relative artifact paths. The `stdin` parameter is never mentioned, and no format examples for argv tokens are given, so compensation is partial.

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 verb and resource: run the `fierce` binary from the OpenCyber enumeration toolkit. An agent can tell this wraps a particular external tool rather than a native operation. It stops short of saying what fierce actually does (DNS/subdomain enumeration), so the purpose is clear as an execution wrapper but not as a capability.

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 description says it runs from the selected engagement namespace and to use relative paths for engagement artifacts, which is setup guidance rather than usage guidance. It never states when to pick this over a sibling such as oc_amass or oc_autorecon, nor any preconditions or exclusions. The agent is left to infer that this is the raw-binary escape hatch.

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