Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_enum4linux_ng

Destructive

Runs enum4linux-ng to enumerate SMB and NetBIOS data such as users, shares, and groups. Executes supplied arguments directly without shell parsing inside an engagement workspace.

Instructions

Run enum4linux ng from the OpenCyber enumeration toolkit. The container executes enum4linux-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_enum4linux_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

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, and the description usefully adds that arguments are passed as discrete argv tokens with no shell parsing, plus the namespace/relative-path execution context. It never explains what the destructive potential actually means or what side effects the scan has on the target, so it adds context but leaves the risk profile thin.

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, each carrying distinct information, with the execution model front-loaded. No filler or repetition.

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 needn't be described, and annotations cover the safety profile. However, for a destructive, open-world enumeration tool with four undocumented parameters and an identically named sibling, the definition should say more about when to choose ng over the classic variant.

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 clarify that 'arguments' are argv tokens (not a shell string) and that paths are relative to the engagement namespace, implicitly covering working_directory and engagement_id, but stdin is left entirely unexplained.

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 specific verb and resource: running enum4linux-ng from the OpenCyber enumeration toolkit, with the argv-based execution model stated up front. It does not explicitly contrast with the sibling oc_enum4linux (classic), so the agent must infer why to pick the ng 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 when-to-use guidance and no named alternative, even though oc_enum4linux exists as a near-identical sibling. The only operational advice is 'use relative paths for engagement artifacts', which is a constraint 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