Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_enum4linux

Destructive

Runs enum4linux with supplied argument tokens for authorized SMB enumeration, executing directly without shell parsing inside an engagement workspace.

Instructions

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

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 openWorldHint=true, destructiveHint=true and idempotentHint=false, so the risk profile is known. The description adds genuinely useful behavior beyond that: argv tokens are executed directly with no shell parsing, which tells the agent how arguments are interpreted, and that execution is scoped to an engagement namespace. It stops short of saying what the tool touches on the target or what output/limits to expect (though an output schema covers the return shape).

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 action and the binary name, then execution semantics, then path convention. No filler, though the execution and path sentences could be tightened into one.

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 annotations cover the risk profile. However, for a destructive, open-world enumeration tool the definition never says what the tool targets or what `arguments` should contain, and it omits any note that this is a mutating/scan-heavy operation on live hosts beyond what hints convey.

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 coverage is 0%, so the description must carry parameter meaning. It does clarify that `arguments` is a raw argv token list with no shell interpretation and that `engagement_id`/`working_directory` are resolved against the selected engagement namespace with relative paths. That covers three of four parameters, but `stdin` is never mentioned and no hint is given about which enum4linux flags are expected in `arguments`, leaving the most important parameter largely 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?

States a specific verb and named binary ("Run enum4linux from the OpenCyber enumeration toolkit"), which is enough to tell it apart from non-enumeration siblings. It does not distinguish itself from the closely named oc_enum4linux_ng sibling, and it never states what enum4linux actually enumerates (SMB/NetBIOS hosts), leaving that to the reader's prior knowledge.

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 an operational constraint ("use relative paths for engagement artifacts") that shapes how the call is made, and implies the tool runs inside an engagement namespace. It offers no when-to-use or when-not guidance and never mentions when the enum4linux_ng variant would be the better choice.

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