Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_qsreplace

Destructive

Replaces query string values with a payload in URLs from stdin, letting you normalize parameters for fuzzing and injection testing. Supply argv tokens directly, no shell parsing.

Instructions

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

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, openWorldHint=true and non-idempotent, so the risk profile is known. The description adds genuinely new behavioral facts beyond that: the binary is executed with argv tokens and shell parsing is never used, and execution is scoped to the selected engagement namespace. It still doesn't say whether output is written to disk or what state a destructive run affects, but the added execution-model detail is substantive.

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, then execution semantics, then scoping. Every sentence carries information; nothing is redundant, though the opening sentence spends words on provenance ('from the OpenCyber web toolkit') that add little for an agent.

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 explained, and the execution model is documented. But the tool's actual function (query-string replacement) and the stdin parameter remain unexplained, which is a real gap for a destructive, open-world tool with zero schema description coverage.

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% across four parameters, so the description must compensate. It partly does: 'supplied argv tokens' clarifies that arguments are passed as an array without shell tokenization, and the engagement-namespace/relative-path sentence implicitly covers engagement_id and working_directory. However, the stdin parameter and the expected format of argv tokens are never mentioned.

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 a specific verb and binary ('Run qsreplace from the OpenCyber web toolkit') and distinguishes the wrapper from a shell-based invocation, but it never says what qsreplace actually does (replacing query-string values in URLs), so an agent unfamiliar with the binary learns only the name. It also offers no explicit differentiation from the dozens of sibling oc_* binaries.

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 no statement of when to choose this tool over alternatives, and no prerequisites or exclusions. The only operational guidance ('use relative paths for engagement artifacts') concerns path conventions, not 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