Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nuclei

Destructive

Run Nuclei scans by passing argv tokens directly without shell parsing in an engagement namespace; use relative paths for engagement artifacts.

Instructions

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

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.7/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 idempotentHint=false, so the risk profile is covered. The description adds genuinely non-obvious behavior beyond that: tokens are passed as discrete argv entries and shell parsing never occurs, which tells the agent not to send a single quoted command string. It omits rate limits and whether output streams, but is solid given annotation coverage.

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 tight sentences with no filler, and the critical argv/no-shell constraint is placed early. The opening clause partially restates the tool name but the rest is dense with information.

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 annotations handle safety. For a 4-parameter wrapper the remaining gap is stdin's purpose and the lack of any note on scanning authorization or duration, but nothing essential to correct invocation is missing.

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 carries the burden. "Supplied argv tokens" effectively explains the arguments array and "relative paths" clarifies working_directory semantics, but stdin — which for a scanner likely carries a target list — is never mentioned, and no parameter is named explicitly.

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?

States a specific verb and resource — "Run nuclei from the OpenCyber web toolkit" — and immediately clarifies the execution model (direct argv, no shell). It does not, however, differentiate this from a generic shell tool like oc_bash, which an agent might reasonably pick to run the same binary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Runs from the selected engagement namespace; use relative paths for engagement artifacts" gives real scoping context for correct invocation, but there is no explicit when-to-use vs. when-not guidance and no named alternative for running the same scanner another way.

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