Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_nikto

Destructive

Run Nikto web server scans within a selected engagement namespace to identify vulnerabilities and misconfigurations using supplied command arguments.

Instructions

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

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.6/5.0
Behavior4/5

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

Annotations already declare destructive, open-world, non-idempotent, non-read-only, so the safety bar is already met by structured data. The description adds genuinely useful behavior beyond that: the container executes `nikto` directly with argv tokens and 'shell parsing is never used', which tells the agent how arguments are interpreted and that shell metacharacters won't work.

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?

Two sentences, front-loaded with the action and then the execution constraint; no filler. Slightly more room could have been used to cover the unexplained parameters without bloat, but nothing present is wasted.

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 no explanation, and annotations cover the destructive/open-world profile. Still, an agent gets no explanation of `stdin`, no guidance on typical nikto argument shape (target specification), and no indication this launches a scanning process with runtime expectations, which is a meaningful gap for a 4-parameter tool.

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?

With 0% schema description coverage, the description must carry all parameter meaning. It explains the `arguments` token semantics (direct argv, no shell) and implies `working_directory` behavior via the relative-path/namespace note, but it says nothing about `engagement_id` or the `stdin` parameter, leaving half the inputs unexplained.

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 gives a specific verb and resource: 'Run nikto from the OpenCyber web toolkit', and clarifies the execution mechanism (direct argv, no shell). It does not differentiate this from siblings such as oc_bash or other scanner wrappers, but the purpose itself is unambiguous.

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?

It states that the run happens 'from the selected engagement namespace' and to 'use relative paths for engagement artifacts', which is real context for how to call it. However, it never says when to choose nikto over alternatives (e.g., a generic shell tool) or any preconditions/exclusions, so guidance is only implied.

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