Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_dnsenum

Destructive

Enumerate DNS records and domain details for authorized engagements by running argument-based DNS enumeration, avoiding shell parsing and storing artifacts in engagement-relative paths.

Instructions

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

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 destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the container invokes the binary directly with argv tokens and never uses shell parsing, which tells an agent that quoting and metacharacters are not interpreted. It does not describe output shape or runtime/rate characteristics, keeping it short of a 5.

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 execution semantics, then path convention. No filler or repetition, though the middle sentence about shell parsing could be tightened slightly.

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 explained, and annotations cover the destructive/open-world profile. Still, for a free-form argv wrapper with zero schema documentation, the description leaves the two required parameters' usage and the tool's actual enumeration behavior underspecified.

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 `arguments` as raw argv tokens (not a shell string) and implies `working_directory` is relative to the engagement namespace, but `engagement_id` and `stdin` are never explained, and the expected argv format (e.g., target host placement) is left unstated.

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: 'Run dnsenum from the OpenCyber enumeration toolkit.' The binary name makes the tool's domain (DNS enumeration) inferable, but the description never states what dnsenum actually does, and it does not differentiate from siblings such as oc_amass or oc_autorecon that also cover reconnaissance.

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?

Gives useful execution context — runs in the selected engagement namespace and relative paths should be used for engagement artifacts — but offers no when-to-use or when-not-to-use guidance relative to other enumeration tools, and no prerequisites (target scope, network reachability) are stated. Usage is implied by the binary name rather than explained.

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