Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_autorecon

Destructive

Executes automated network reconnaissance with explicit argument tokens in an engagement workspace, enabling scoped target discovery and artifact generation without shell parsing.

Instructions

Run autorecon from the OpenCyber network toolkit. The container executes autorecon 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_autorecon"
  }
}

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, openWorld=true and idempotent=false, so the risk profile is covered. The description adds genuinely non-obvious behavior: argv is passed directly with no shell parsing, and execution is scoped to the selected engagement namespace with relative artifact paths. It stops short of saying what autorecon will actually touch or how output is surfaced, but that gap is partly offset by the existing output schema.

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 identity of the tool, then the execution model, then the path/namespace rule. No filler, though the argv/no-shell sentence could be tightened.

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, a tool that executes an arbitrary scanner with user-supplied argv leaves the agent without guidance on stdin, expected argument shapes, or the consequences of a destructive run beyond the hint flag.

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 does partially, clarifying that 'arguments' are raw argv tokens with no shell interpretation and implying 'working_directory'/'engagement_id' semantics via the namespace and relative-path statements. 'stdin' is never mentioned and no parameter formats or examples are given, so the coverage gap is only partly closed.

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 ('Run') and a specific resource ('autorecon from the OpenCyber network toolkit'), which is enough to distinguish it from wrappers of other tools such as oc_amass or oc_aircrack. It does not, however, contrast itself with any closely related sibling or scope variant.

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 explicit statement of when to choose this tool over alternatives, nor any prerequisite or exclusion. The only operational hints ('runs from the selected engagement namespace', 'use relative paths') are invocation mechanics 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