High Risk →

sqlmap_scan

Execute SQLmap SQL injection scanner.

How to control sqlmap_scan ↓

AI agents invoke sqlmap_scan to trigger actions in Kali Security MCP. 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.

High Risk

SQLmap is an automated SQL injection tool that actively probes and exploits database vulnerabilities. It executes attacks against target systems (including data extraction, authentication bypass, and potentially OS command execution via SQL injection). On a penetration testing server, misuse could lead to unauthorized database access, data exfiltration, or full system compromise.

From the tool's definition Execute SQLmap SQL injection scanner

Documented attack patterns abuse exactly the kind of access sqlmap_scan gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for sqlmap_scan:

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

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.

  1. Create a free account and register Kali Security MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the sqlmap_scan tool do? +

Execute SQLmap SQL injection scanner. It is categorised as a Execute tool in the Kali Security MCP 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 Security 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 Security MCP. 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 Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kali Security MCP tool call.

Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.