Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hash_identifier

Destructive

Identifies unknown hash types from credential artifacts by running hash-identifier with supplied arguments in an isolated engagement workspace, without shell parsing.

Instructions

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

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?

The description adds real behavioral context beyond the annotations: direct exec with argv tokens, no shell parsing, and running from the selected engagement namespace. However, despite destructiveHint=true and idempotentHint=false, it never explains what could be destroyed or how repeated calls differ, so a material safety gap remains.

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 sentences, front-loaded with the action and followed by execution-model details. Little waste; the namespace and path sentences could be merged but each carries distinct operational information.

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. The description covers the execution model, security posture of argument passing, and working-directory expectations; the main omissions are the undocumented `stdin` parameter and any hint about why the call is marked destructive.

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 partially does: 'supplied argv tokens' explains `arguments`, 'engagement namespace' implies `engagement_id`, and 'relative paths for engagement artifacts' implies `working_directory`. The `stdin` parameter is never mentioned, leaving one of four undocumented.

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 states a concrete verb and resource: it runs the `hash-identifier` binary from the OpenCyber credentials toolkit with supplied argv tokens. That is specific enough to distinguish it from sibling wrappers like oc_aircrack or oc_amass, though it never explicitly contrasts itself with them.

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 explicit when-to-use statement, no when-not-to-use, and no named alternative. The only operational guidance is about paths ('use relative paths for engagement artifacts') and namespace selection, which is execution guidance rather than tool-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