Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hashpump

Destructive

Runs hashpump with supplied arguments to execute hash length extension attacks for signature forgery testing, using direct argv execution without shell parsing.

Instructions

Run hashpump from the OpenCyber forensics toolkit. The container executes hashpump 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_hashpump"
  }
}

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

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: argv is passed directly with no shell parsing (relevant for injection-sensitive inputs) and execution is scoped to the engagement namespace. It stops short of saying what a destructive run could modify or what permissions are needed, which is the main remaining gap.

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 tight sentences, front-loaded with what runs and how it is executed, with the namespace/path constraint following. No filler, though the brevity is partly under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but the definition leaves a four-parameter tool with zero schema coverage largely unexplained and never states what hashpump produces or what side effects a destructive run has. For an arbitrary-argv, destructive binary wrapper this is thin.

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 description coverage is 0%, so the description must carry all four parameters. It only indirectly explains `arguments` ('supplied argv tokens') and implies `engagement_id`/`working_directory` via the namespace and relative-path sentences; `stdin` is never mentioned at all. Roughly half the parameters remain undocumented in both schema and description.

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 executable (`hashpump`) and its toolkit wrapper, plus the execution mechanism (direct argv, no shell). It does not state what hashpump actually does (hash length-extension attacks), so an agent unfamiliar with the binary knows the verb but not the outcome; the executable name still separates it cleanly from siblings like oc_bash or oc_angr_analyze.

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 no statement of when to use this tool versus oc_bash or other forensics wrappers, and no prerequisites or exclusions. The only guidance offered is environmental (engagement namespace, relative paths), which is invocation mechanics rather than selection guidance.

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