Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_recon_ng

Destructive

Runs Recon-ng enumeration commands within an engagement namespace, executing supplied argv tokens without shell parsing and storing artifacts in the engagement workspace.

Instructions

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

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

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

The annotations already declare destructive, openWorld, non-idempotent, and non-readOnly behavior. The description adds useful execution details: direct argv execution and no shell parsing. It does not explain the scope of destructive actions recon-ng may perform, so it adds context but not full behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences, front-loaded with purpose and followed by execution constraints. Every clause adds useful information without restating schema details unnecessarily.

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 tool has an output schema and rich annotations, so the description need not explain return values or safety hints. It covers purpose, execution method, and namespace/path conventions, but leaves the optional stdin parameter and exact argument conventions undocumented. This is adequate but not fully complete for a destructive CLI-wrapper tool.

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 are argv tokens, that engagement_id selects the engagement namespace, and that working_directory should use relative paths for artifacts. It does not explain stdin semantics or give more detail on working_directory format.

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 states a specific verb and resource: run recon-ng from the OpenCyber enumeration toolkit. It explains that the container executes recon-ng directly with supplied argv tokens, but it does not explicitly distinguish this tool from sibling enumeration tools.

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?

It gives execution context such as running from the selected engagement namespace and using relative paths for engagement artifacts. However, it does not say when to choose this tool over sibling enumeration tools or when not to use it.

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