Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

sqlmap_scan

Tests target URLs for SQL injection vulnerabilities using SQLMap, supporting GET requests and optional POST data.

Instructions

Use SQLMap to test for SQL injection vulnerabilities

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": {
      "url": "<url>"
    },
    "name": "sqlmap_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL to test (e.g., http://example.com/page?id=1)
dataNoPOST data if using POST method
methodNoHTTP method: GET or POSTGET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say the scan is active and sends attack payloads, that it may be slow or intrusive, that authorization is required, or that it could alter target data. For an offensive security tool with zero annotation coverage, this is a substantial gap.

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?

One short sentence with the verb and vulnerability class front-loaded and no filler. It is efficient, though its brevity is under-specification rather than deliberate economy, which keeps it from a 5.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an intrusive scanning tool with no annotations and no output schema, the description omits what the tool returns (findings, injectable parameters), how long a run takes, and the safety caveats an agent needs before invoking it. Only the purpose is covered, which is not enough for this complexity.

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 100%, with each of the three parameters documented, including a concrete URL example and GET/POST semantics. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 concrete verb and target class: use SQLMap to test for SQL injection vulnerabilities. That is specific enough to separate it from siblings such as nikto_scan or nmap_scan, which cover other vulnerability classes. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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 guidance on when to choose this over nikto_scan or nmap_scan, no prerequisites (such as an injectable-looking parameter or an authorized target), and no exclusions. The agent must infer activation conditions entirely from the tool name and the phrase 'SQL injection'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.