Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_responder

Destructive

Run Responder in an isolated engagement namespace for LLMNR, NBT-NS and mDNS poisoning and credential capture, passing argv tokens directly without shell parsing.

Instructions

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

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

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false. Beyond that, the description adds meaningful execution semantics: no shell parsing (so no pipes/redirects/globbing), the process runs from the engagement namespace, and relative artifact paths are expected. It does not say what responder actually affects on the network or what happens on failure.

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?

Three compact sentences, each front-loaded with a distinct fact: what runs, how it executes, and where it executes. No filler or restatement of the title.

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 explained. However, with 0% schema coverage on four parameters, the definition omits stdin and working_directory handling, and it never states what responder is used for (credential/LLMNR-NBT-NS poisoning) — an agent unfamiliar with the binary leaves understanding to external knowledge.

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 carries the burden. It clarifies that 'arguments' are raw argv tokens (not shell-parsed) and that execution happens relative to the engagement namespace, which partially explains working_directory and engagement_id. stdin is never mentioned, leaving one of four parameters 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 names a specific verb ('Run') and resource ('responder from the OpenCyber enumeration toolkit'), so the agent knows exactly which binary is being invoked. It implicitly distinguishes itself from the generic shell sibling by stating that argv tokens are executed directly, though it never explicitly names an alternative.

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?

Usage is implied by the wording 'Run responder' and there is a concrete operational constraint ('use relative paths for engagement artifacts'), plus an implicit context that the tool runs inside a selected engagement namespace. There is no explicit when-to-use vs. when-not guidance and no named alternatives.

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