Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_john

Destructive

Execute password-cracking commands with supplied arguments in an isolated engagement workspace, using relative paths for artifacts and optional stdin.

Instructions

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

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 flag destructiveHint=true, openWorldHint=true, and non-idempotent, so the safety profile is covered. The description adds genuinely new behavior: argv tokens are passed directly with no shell parsing, which tells the agent that quoting/escaping semantics differ from a shell, and that execution is scoped to the engagement namespace.

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 what runs before the execution and path details. Nothing is redundant, though the sentence about the container could be folded more tightly.

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 annotations cover the safety profile. The main remaining hole is the silent `stdin` parameter for a tool that plausibly accepts wordlists or hashes on input.

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 burden. It explains `arguments` as argv tokens passed verbatim, ties relative paths to `working_directory`, and connects `engagement_id` to the engagement namespace, but `stdin` is never mentioned. Three of four parameters get meaning, leaving one gap.

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 `john` tool from the OpenCyber credentials toolkit. The tool name plus the description make it unmistakable which binary is being invoked, though it never contrasts itself with credential-related siblings.

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?

No explicit guidance about when to reach for this tool versus other credential/attack tools, and no prerequisites or exclusions. It does give operational context (engagement namespace, relative paths for artifacts), which implies the usage setting but stops short of when-to-use 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