Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_dalfox

Destructive

Execute dalfox XSS scans using supplied CLI arguments in the selected engagement namespace; direct tokens avoid shell parsing and relative paths target engagement artifacts.

Instructions

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

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

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

Annotations already declare destructive=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds useful execution context by noting argv-token execution with no shell parsing and operation from the selected engagement namespace, but it does not explain scan side effects, output handling, or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with no wasted wording. Execution semantics and path guidance are front-loaded.

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?

For a destructive command-execution wrapper, the description covers the key execution model and working-directory expectations, while annotations and the output schema carry safety and return-value information. It remains incomplete because it does not explain what dalfox does, when to use it, or the meaning of all four parameters.

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 must carry parameter meaning, and it partially does: it clarifies that `arguments` are argv tokens and that `working_directory` should use relative paths for engagement artifacts. It leaves `engagement_id` and `stdin` largely unexplained, which is a clear gap.

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 verb and resource: run `dalfox` from the OpenCyber web toolkit. It clearly identifies the wrapped binary among many sibling `oc_*` tools, though it does not explain what dalfox itself is used for.

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?

The description gives a practical path guideline, telling callers to use relative paths for engagement artifacts. However, it provides no guidance on when to choose this tool versus alternatives, nor any preconditions or exclusions.

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