Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_wpscan

Destructive

Run WordPress vulnerability scans with wpscan using supplied arguments in an engagement-scoped workspace, with no shell parsing and relative artifact paths.

Instructions

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

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

A3.5/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 safety profile is carried by structured data. The description adds genuinely new behavioral facts beyond that: argv tokens are passed directly with no shell parsing (so no metacharacter injection or quoting semantics), execution is containerized, and the working scope is the engagement namespace. It does not disclose auth/API-token needs or rate-limit/network-egress behavior, which would be the remaining useful additions.

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 the execution-model caveat, then the path/namespace rule. No filler, though the two sentences about execution and paths could be tightened into one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 destructive/open-world annotations cover the risk profile. Added detail on the no-shell execution model and namespace-relative paths makes the definition sufficient for correct invocation. The main omission is what the underlying scanner is for and any credential requirements, though an agent targeting WordPress scanning would already know.

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 has to compensate. It does add meaning for `arguments` (raw argv tokens, not a shell string) and for `working_directory` via the relative-path rule, but `stdin` and `engagement_id` receive no explanation of expected format or effect. Partially compensates for the coverage gap, leaving real holes.

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 names a specific verb and resource: execute `wpscan` via the OpenCyber container. It also clarifies the execution model (direct argv, no shell), which lets an agent distinguish this from a generic shell wrapper. It stops short of saying what wpscan actually does (WordPress enumeration/vulnerability scanning), which matters for agents unfamiliar with the binary.

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 explicit when-to-use or when-not-to-use guidance, and no routing hint toward an alternative such as a generic shell tool. The only usage-shaped instruction is 'use relative paths for engagement artifacts' and the note that it runs from the selected engagement namespace, which is operational advice rather than selection guidance.

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