sqlmap_scan

Test for SQL injection vulnerabilities with SQLMap

SERVERKali Linux MCP Server SOURCEalessandroannini/kali-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/alessandroannini-kali-mcp-server/sqlmap-scan.md

WHAT IT DOES

What sqlmap_scan does on Kali Linux MCP Server

AI agents invoke sqlmap_scan to trigger actions in Kali Linux MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why sqlmap_scan is rated High

SQLMap executes active SQL injection attacks against databases, which can extract data, modify records, and in some configurations achieve remote code execution. It runs external attack tooling with effects entirely dependent on arguments (target URL, parameters, aggression level).

From the tool's definition 'Test for SQL injection vulnerabilities with SQLMap' — SQLMap actively probes and exploits SQL injection vulnerabilities against target systems

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sqlmap_scan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Linux MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sqlmap_scan, this is the rule to start with:

sqlmap_scan Rate-limited

sqlmap_scan stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sqlmap_scan": {
      "limits": [
        {
          "counter": "sqlmap_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kali Linux MCP Server, apply this rule, and every sqlmap_scan call is checked against it from then on.

FAQ

Questions about sqlmap_scan

What does the sqlmap_scan tool do? +

Test for SQL injection vulnerabilities with SQLMap. It is categorised as a Execute tool in the Kali Linux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sqlmap_scan? +

Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for sqlmap_scan: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kali Linux MCP Server. Nothing to install.

What risk level is sqlmap_scan? +

sqlmap_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sqlmap_scan? +

Yes. Add a rate_limit block to the sqlmap_scan rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block sqlmap_scan completely? +

Set action: deny in the PolicyLayer policy for sqlmap_scan. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides sqlmap_scan? +

sqlmap_scan is provided by the Kali Linux MCP Server MCP server (alessandroannini/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Kali Linux MCP Server, and thousands of servers like it.

This server

All 14 Kali Linux MCP Server tools → High-risk tools on this server →

Across the catalogue

run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →