Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_arjun

Destructive

Runs Arjun parameter discovery against target URLs using direct argv execution inside an engagement namespace, without shell parsing.

Instructions

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

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

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

Annotations already declare destructive, non-idempotent, and open-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact: arguments are passed as argv tokens with no shell parsing. It does not warn about the destructive impact on targets, output volume, or runtime.

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 what the tool does, and every sentence carries information. No preamble or filler.

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 no explanation, and the description covers execution model, namespace scoping, and path conventions. Remaining gap is that it never says what arjun is or when to reach for it, which matters for an agent unfamiliar with the toolkit.

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 coverage is 0%, so the description has to carry the load. It meaningfully clarifies 'arguments' (raw argv tokens to arjun, no shell interpretation) and ties 'working_directory' to relative engagement paths and 'engagement_id' to the namespace, but the 'stdin' parameter is never mentioned.

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 arjun from the OpenCyber web toolkit,' and explains it executes the arjun binary with argv tokens. It is identifiable against siblings like oc_bash because no shell parsing is involved, though it assumes the agent already knows what arjun does.

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?

Gives context for invocation – it runs in the selected engagement namespace and requires relative paths for engagement artifacts – but never states when to choose arjun over sibling recon tools or what prerequisites (target scope, authorization) apply before running a destructive scan.

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