Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_smbmap

Destructive

Execute smbmap against SMB targets within an engagement workspace to enumerate shares and permissions using direct argv tokens, avoiding shell parsing.

Instructions

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

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 non-idempotent behavior, so the safety bar is lower. The description adds real execution context — no shell parsing, runs in the engagement namespace, relative-path resolution for artifacts — but does not explain what the destructive capability means in practice (e.g. write/upload actions against remote shares) or what network exposure to expect.

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 tool identity and execution model, with no filler. The invocation-safety note is placed before the namespace/path note, which is the right ordering for an agent deciding how to construct a call.

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 described, and the description covers execution model, namespace, and path resolution adequately for a wrapper tool. The gaps are the unexplained `stdin` parameter and the absence of any statement about what the tool actually enumerates or when to prefer it.

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 parameter meaning, and it partially does: `arguments` is characterized as raw argv tokens with no shell interpretation, `working_directory` as relative to engagement artifacts, and `engagement_id` as selecting the namespace. The `stdin` parameter is left completely unexplained, and no argument syntax 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 names a specific verb and resource: it runs the `smbmap` binary from the OpenCyber toolkit, which an agent can distinguish from unrelated siblings like oc_bash or oc_arp_scan. It stops short of differentiating from other SMB/enumeration siblings or stating what smbmap is used for, so it is clear but not maximally distinguishing.

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 invocation guidance ('argv tokens', 'shell parsing is never used', 'use relative paths'), but no guidance on when to choose this tool over alternatives such as a generic shell tool, nor any stated prerequisites or exclusions. The agent must infer the use case entirely.

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