Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ropper

Destructive

Execute ropper directly to analyze binaries and locate ROP gadgets without shell parsing, using engagement-scoped artifact paths.

Instructions

Run ropper from the OpenCyber binary toolkit. The container executes ropper 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_ropper"
  }
}

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

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

Adds genuinely useful context beyond the annotations: the container executes ropper directly with argv tokens and never uses shell parsing, and execution is scoped to the engagement namespace. However, with destructiveHint=true and readOnlyHint=false declared, the description never explains what could be destroyed or what side effects an analysis run may have, leaving that mismatch unaddressed.

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 followed by the execution model and path convention. No filler; the only weakness is that a brief clause on what ropper does would be worth the words.

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?

An output schema exists, so return values need no explanation, and the invocation model is adequately covered. Gaps remain for a tool with a destructive annotation and an undocumented stdin parameter: an agent cannot tell what the destructive flag implies or how to feed input via stdin.

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 implicitly explains `arguments` (argv tokens), `engagement_id` (selected engagement namespace) and `working_directory` (relative paths for artifacts), but says nothing about the optional `stdin` parameter, leaving one of four parameters undocumented anywhere.

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 `ropper` from the OpenCyber binary toolkit with the supplied argv. It is clearly a wrapper invocation and distinguishable from other oc_* wrappers by naming the underlying binary, though it never says what ropper is for (ROP gadget discovery), which an agent unfamiliar with the tool would need.

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 partial operational guidance: runs in the selected engagement namespace and relative paths should be used for engagement artifacts. It offers no when-to-use vs when-not guidance and does not point to any sibling alternative for related binary-analysis tasks, so usage must be inferred.

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