Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_medusa

Destructive

Runs Medusa credential-testing commands in an isolated engagement namespace, passing arguments directly without shell parsing and resolving artifacts via relative paths.

Instructions

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

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.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, non-idempotent. The description adds genuinely new behavioral context: arguments are passed as argv tokens with no shell parsing (so quoting/injection semantics differ from a shell tool), and execution is anchored to the engagement namespace with relative-path resolution for artifacts. It omits typical side effects of a brute-force run (account lockouts, network noise), which would have made this a 5.

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 short sentences, front-loaded with the action and free of filler. The final sentence is slightly compressed and reads as two ideas (namespace selection plus relative paths) stacked together.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the annotations cover the safety profile. The description fills the remaining gap an agent needs to call it safely: how arguments are delivered, where the process runs, and how paths resolve.

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 load. It explains `arguments` (raw argv, no shell), `working_directory` (relative to engagement namespace), and `engagement_id` implicitly via namespace selection, but says nothing about `stdin`, leaving one of four parameters with no meaning beyond its name.

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 medusa from the OpenCyber credentials toolkit', and clarifies the execution model (direct argv tokens, no shell parsing). That execution detail also implicitly separates it from a generic shell tool like oc_bash, though no sibling is named explicitly.

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?

Offers operational guidance ('runs from the selected engagement namespace', 'use relative paths for engagement artifacts') but no explicit when-to-use / when-not-to-use versus alternatives and no stated preconditions such as required credentials or target authorization. Usage is only implied by the tool's nature.

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