Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_zap

Destructive

Execute zaproxy commands with supplied arguments in a selected engagement workspace to run authorized web security scans without shell parsing.

Instructions

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

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

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

The description adds useful implementation behavior: it executes `zaproxy` directly with argv tokens and never uses shell parsing, and it runs from the selected engagement namespace with relative paths. However, it does not disclose the destructive, open-world, non-idempotent effects already flagged in annotations, nor does it explain what the arguments actually control.

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?

The description is short and front-loaded, with no filler. It could be slightly more structured by explicitly mapping the argv and path guidance to the relevant parameters, but it is efficient overall.

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?

The definition has an output schema and annotations covering safety, so it need not explain return values. For a raw command-execution tool with four parameters and zero schema descriptions, however, the description leaves too much parameter and impact context implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate for four undocumented parameters. It explains that `arguments` are raw argv tokens and that relative paths are relative to the engagement namespace, but it does not clarify `engagement_id`, `stdin`, or `working_directory`, leaving important usage semantics unstated.

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?

The description states a specific action and resource: running `zaproxy` via the OpenCyber web toolkit. It is distinguishable from sibling tools by naming zap/zaproxy directly, though it does not spell out OWASP ZAP or the tool's security-testing role.

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?

It gives limited context about execution from the engagement namespace and using relative paths, but does not say when to choose this tool over alternatives, when not to use it, or any preconditions for running zaproxy.

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