Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hashcat

Destructive

Executes hashcat with supplied argv tokens in an engagement workspace, avoiding shell parsing while cracking hashes from relative artifact paths.

Instructions

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

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 and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavior: arguments are passed as discrete argv tokens with no shell parsing, and execution is scoped to an engagement namespace — both material facts for constructing a call. It stops short of saying what files hashcat may overwrite or how long a run may take.

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 action and followed by the execution and path-scoping constraints. No filler, though the argv/no-shell point and the path point could be merged into one sentence without losing 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 described, and the annotations cover destructiveness and open-world behavior. Remaining gaps are the undocumented 'stdin' parameter and the absence of any note on expected runtime or output artifacts for a long-running cracking job.

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 parameter burden. It clarifies that 'arguments' are argv tokens (not a shell string), ties 'engagement_id' to the selected engagement namespace, and orients 'working_directory' toward relative engagement artifact paths. 'stdin' is left entirely unexplained, which is a real gap at 0% schema coverage.

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+resource ('Run hashcat') and adds the distinguishing execution detail that the container invokes hashcat directly with argv tokens rather than through a shell. That detail implicitly separates it from a general shell tool like oc_bash, though it never names an alternative outright.

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?

Implies usage context ('from the selected engagement namespace', 'use relative paths for engagement artifacts') which tells an agent how to call it correctly. It gives no explicit when-to-use/when-not guidance and does not say when to prefer a sibling such as oc_bash or how to choose between them.

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