Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ophcrack

Destructive

Crack Windows password hashes in an isolated engagement workspace by passing direct argv tokens, supporting authorized credential recovery and password auditing.

Instructions

Run ophcrack from the OpenCyber credentials toolkit. The container executes ophcrack 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_ophcrack"
  }
}

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 idempotentHint=false. The description adds genuine value by disclosing that shell parsing is never used, so argv is passed literally, and that execution is scoped to the engagement namespace. It does not mention that ophcrack writes crack session/rainbow-table artifacts to disk or any runtime caveats, which is a notable omission for a destructive tool.

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?

Two compact sentences with the execution model front-loaded and the path convention second. No filler, though the second sentence mixes namespace and path guidance in a way that could be split for clarity.

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 the invocation model (argv, no shell, engagement namespace) is covered. What remains missing is the tool's actual purpose and any warning about on-disk artifacts, but for a thin binary wrapper this is close to complete.

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% across four parameters, so the description must compensate. It explains the `arguments` array (raw argv tokens, no shell interpretation) and partially covers `working_directory`/`engagement_id` via the relative-path and namespace note, but `stdin` is never mentioned and the default working directory behavior is left implicit.

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 resource: run the `ophcrack` binary from the OpenCyber credentials toolkit, executed with argv tokens. An agent can distinguish it from siblings like oc_aircrack or oc_bash because it names the exact executable. It stops short of saying what ophcrack actually does (crack Windows/LM/NTLM hashes), so an agent unfamiliar with the binary gets the wrapper but not the capability.

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?

The only guidance is 'use relative paths for engagement artifacts' and that it runs from the selected engagement namespace. There is no statement of when to choose this over oc_aircrack, oc_bash, or any other credential tool, and no exclusions or preconditions (e.g. hash file must exist, rainbow tables required).

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