Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_sqlmap

Destructive

Executes sqlmap directly with supplied arguments in an engagement namespace for authorized SQL injection testing; supports stdin and relative artifact paths without shell parsing.

Instructions

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

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.4/5.0
Behavior3/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 risk profile is covered. The description adds genuinely useful execution semantics — argv tokens are passed directly and shell parsing is never used, so no shell metacharacter interpretation occurs — but says nothing about scope, impact of a destructive run, or rate/timeout behavior.

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 execution model, then environment convention. Little waste; only the path convention sentence borders on boilerplate for this tool family.

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 not be described. However, for a destructive, open-world tool with zero schema coverage on four parameters, the description does not show how argv should be shaped (e.g., flag passing, target specification) or what the engagement namespace constrains — an agent can call it but must guess at argument conventions.

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. It maps indirectly to three parameters ('supplied argv tokens' → arguments, 'engagement namespace' → engagement_id, 'relative paths' → working_directory) but gives no format, example argv, or explanation of stdin, leaving a real 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?

States a concrete verb+resource: 'Run sqlmap from the OpenCyber web toolkit.' The tool name and description make its identity unambiguous relative to the other oc_* scanner wrappers, though it never names a sibling or contrast case.

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?

Provides operational context ('runs from the selected engagement namespace; use relative paths for engagement artifacts') that implies when this is the right tool, but gives no explicit when-to-use/when-not guidance or alternatives for SQL-injection testing versus other scanners.

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