Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_xsser

Destructive

Runs cross-site scripting scans with supplied argument tokens inside an engagement namespace for authorized testing, using relative paths for workspace artifacts.

Instructions

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

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, non-idempotent and non-read-only, so the risk profile is covered. The description adds real behavioral context beyond that: argv tokens are passed directly with no shell parsing (so no shell metacharacter interpretation), execution is scoped to the selected engagement namespace, and artifact paths should be relative. It stops short of mentioning timeouts, output capture, or what happens on failure.

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 mechanism, with no filler. The argv/no-shell-parsing sentence is the most valuable and is well placed; nothing is redundant.

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, and the wrapper nature keeps complexity low. Still, with zero schema description coverage the description should cover all four parameters and say something about how the invoked binary's results are captured; `stdin` and failure behavior are left unaddressed.

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 must carry parameter meaning. It clarifies that `arguments` is a raw argv token array and implicitly explains `working_directory` and `engagement_id` via the relative-path and namespace sentences, but it never mentions `stdin`, leaving one of four parameters entirely undefined in both schema and text. Partial compensation only.

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 states a concrete verb and resource ("Run xsser") and adds that execution happens in a container from the OpenCyber web toolkit. However, it never says what xsser actually is or does (XSS scanning/fuzzing), so an agent unfamiliar with the binary learns little beyond the name it already sees in oc_xsser. It is specific about mechanism but thin on capability.

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 when-to-use guidance, no condition under which this tool is preferred over alternatives, and no exclusions. The remaining sentences are execution mechanics (argv tokens, namespace, relative paths) rather than selection guidance. The agent must already know it wants xsser.

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