Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_jaeles

Destructive

Run jaeles scans inside an engagement namespace by passing argv tokens directly, without shell parsing, and use relative paths for engagement artifacts.

Instructions

Run jaeles from the OpenCyber web toolkit. The container executes jaeles 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_jaeles"
  }
}

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

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

Annotations already declare destructive, open-world, non-read-only, non-idempotent behavior. The description adds meaningful execution semantics beyond them: direct argv execution with no shell parsing and operation inside the selected engagement namespace with relative paths. It still omits side effects, but the annotations carry the safety profile.

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 are front-loaded with the core action and execution model, and each adds operational information. There is little wasted wording, though 'from the OpenCyber web toolkit' is slightly redundant with the name.

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

Completeness3/5

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

For a destructive command runner, the definition explains the execution model and namespace behavior, and the output schema covers return values. However, it does not say what jaeles is used for or clarify stdin, leaving an agent to infer important invocation details from prior knowledge.

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?

With 0% schema description coverage, the description must carry parameter meaning. It maps 'supplied argv tokens' to arguments, 'selected engagement namespace' to engagement_id, and relative engagement paths to working_directory, but it never explains stdin or gives format/default details. This is partial compensation for a four-parameter schema.

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 uses the specific verb 'Run' with the resource 'jaeles' and identifies the OpenCyber toolkit execution context. It does not differentiate this from siblings such as oc_bash or other security tools, but the tool name and description make its narrow purpose clear.

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?

It states the execution namespace and relative-path convention, but gives no guidance on when to choose this tool over oc_bash or other siblings, nor any exclusions or prerequisites. Operational path guidance is not the same as 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