Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_pwninit

Destructive

Run pwninit with explicit arguments in an isolated engagement workspace to patch challenge binaries against a target libc and prepare exploit files.

Instructions

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

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

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

Annotations already declare destructiveHint=true, non-idempotent, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: shell parsing is never used (argv tokens go straight to exec), which matters for quoting and injection, and execution is scoped to the engagement namespace with relative artifact paths. It does not state what is mutated in place despite the destructive flag, which keeps it from 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 sentences, front-loaded with the action and execution model, with no filler. Slightly terse given the missing 'what this does' clause, but nothing is wasted.

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 not be described. But for a destructive binary-patching tool, the definition omits what pwninit modifies or produces on disk, which an agent needs before running it against engagement artifacts. Execution mechanics are well covered; effects are not.

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 clarifies 'arguments' as raw argv tokens passed to exec (no shell splitting) and ties engagement_id to a namespace with relative-path resolution. It says nothing about 'stdin' or 'working_directory', leaving half the parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the binary being wrapped (pwninit) and states it runs with supplied argv tokens, so the mechanical purpose is identifiable. However, it never says what pwninit actually does (patching challenge binaries, wiring interpreter/loader), so an agent unfamiliar with the tool gets only the name restated as a wrapper. It also gives no basis for distinguishing this from other oc_* binary wrappers.

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?

There is operational guidance about relative paths and the engagement namespace, but nothing on when to choose this tool versus siblings or what preconditions must hold before invoking it. The one contextual hint (relative paths for artifacts) is about path form, not about tool selection.

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