Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_network_mapper

Destructive

Run netdiscover network mapping with explicit argv tokens in an engagement's isolated namespace to discover live hosts and map subnets during authorized security assessments.

Instructions

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

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the risk profile is covered structurally. The description adds genuinely useful context beyond that — that netdiscover is executed directly with argv tokens and never through a shell — but says nothing about the effects of scanning (traffic emitted, target scope) that the openWorld/destructive hints imply.

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 with the tool identity front-loaded and no filler. The no-shell-parsing note is well placed; the path sentence is slightly fragmented but earns its place.

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 described, and the annotations carry the safety profile. However, for a destructive, open-world tool with an opaque free-form argv parameter and zero schema coverage, the description leaves the agent without concrete argument syntax or scope expectations.

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 must carry the burden. It clarifies that `arguments` is a list of argv tokens passed directly to netdiscover, and hints that `working_directory` should be relative to the engagement namespace, but `engagement_id` and `stdin` are never explained and no argv 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?

The description gives a concrete verb and resource ('Run network mapper') and, crucially, names the underlying binary (`netdiscover`), so the agent knows exactly what class of discovery is performed. It does not distinguish itself from sibling reconnaissance tools like oc_arp_scan or oc_autorecon, which keeps it from a 5.

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 only guidance is operational ('Runs from the selected engagement namespace; use relative paths for engagement artifacts'), which explains how to invoke rather than when to choose this over alternatives. There is no statement of when-not-to-use or which sibling tool to pick instead.

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