Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_netexec

Destructive

Run NetExec enumeration commands with direct argv execution and no shell parsing inside an engagement workspace; use relative paths for scoped artifacts.

Instructions

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

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

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

Annotations already declare destructive=true, openWorld=true, idempotent=false and readOnly=false, so the risk profile is covered. The description adds genuinely non-obvious execution semantics: argv tokens are passed directly to `nxc` and shell parsing is never used, meaning pipes, redirection, and shell metacharacters will not work. That is a substantive behavioral detail an agent could otherwise get wrong.

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?

Two short sentences, front-loaded with the action, then the execution mechanics, then the scoping constraint. No filler and no restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 risk. The remaining gap is operational detail for a destructive open-world tool: no note on whether engagement_id must pre-exist, whether targets must be inside engagement scope, or how failures/timeouts surface.

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 coverage is 0%, so the description must carry parameter meaning and it partially does: `arguments` is clarified as raw argv tokens, `engagement_id` as selecting the engagement namespace, and `working_directory` as the base for relative artifact paths. The `stdin` parameter is never mentioned, and there is no guidance on how arguments should be formatted beyond token-per-element.

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?

It states a specific verb and resource ('Run netexec from the OpenCyber enumeration toolkit') and names the underlying binary `nxc`, so the agent knows exactly what executes. It stops short of contrasting this with any sibling, relying on the tool name and binary family to imply where it fits.

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?

Implicitly places the tool in an enumeration context within an engagement namespace and tells the caller to use relative paths for engagement artifacts, which is useful operating guidance. It gives no explicit when-to-use versus when-not guidance, no prerequisites, and no mention of authorization or target scoping requirements that matter for an offensive tool.

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