Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_subfinder

Destructive

Run subfinder with explicit arguments in an engagement workspace to enumerate subdomains for authorized reconnaissance.

Instructions

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

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.6/5.0
Behavior4/5

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

Annotations already declare destructive, openWorld, and non-idempotent behavior, so the description is not burdened with the safety profile. It still adds real execution semantics: argv tokens are passed directly to subfinder with no shell parsing, and execution is scoped to the selected engagement namespace with relative artifact paths.

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 tight sentences, front-loaded with the purpose and followed by the two operational constraints that matter most. Nothing is redundant, though the split of execution detail across sentences could be slightly more structured.

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. Gaps remain around the undocumented stdin parameter and the absence of guidance on what subfinder flags or output artifacts to expect from an arbitrary-argv wrapper.

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 parameter meaning. It clarifies that 'arguments' is a raw argv token list and that 'working_directory' should be relative to the engagement, and it implies 'engagement_id' scopes the namespace, but 'stdin' is never mentioned and no argument format examples are given.

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 subfinder') and identifies the OpenCyber toolkit context, so the agent knows exactly what executes. It does not distinguish subfinder from similarly named enumeration siblings such as oc_amass or oc_autorecon, leaving that choice to the agent.

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?

Usage is implied by the enumeration-toolkit framing, and the note to use relative paths for engagement artifacts is practical guidance. However, there is no explicit when-to-use versus when-not-to-use statement, nor any routing to alternative enumeration tools.

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