Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nmap

Destructive

Run Nmap scans inside an engagement workspace using explicit argv tokens without shell parsing, enabling authorized network discovery and service enumeration with relative artifact paths.

Instructions

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

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 destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is covered structurally. The description adds genuinely new behavior: argv tokens are passed directly and 'shell parsing is never used,' which tells the agent pipes/redirection/quoting tricks will not work. It stops short of covering timeouts, output capture, or resource limits.

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 action and immediately followed by the most consequential execution detail (no shell parsing). 'from the OpenCyber network toolkit' is the only mildly redundant clause.

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 plus rich annotations mean the description needn't explain returns or safety. However, for a destructive, open-world execution wrapper with zero schema documentation, it should say more about stdin handling and invocation limits to be fully adequate.

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 param meaning; it clarifies that 'arguments' means raw argv tokens (implying no shell metacharacters) and hints at working_directory via relative-path guidance. It says nothing about 'stdin', the default working_directory value, or what engagement_id scopes — leaving real gaps for two of four params.

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 both a specific verb and resource: 'Run nmap' and 'executes nmap directly with the supplied argv tokens.' The scope is unambiguous, though it never contrasts itself with scanning-adjacent siblings (e.g. oc_arp_scan, oc_autorecon); the distinct binary name is what separates it.

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 operational context ('runs from the selected engagement namespace', 'use relative paths for engagement artifacts') but no explicit when-to-use/when-not or alternative-selection guidance. Implied usage as a raw network scanner is inferable from the tool name alone.

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