sqlmap_run

Automated SQL injection suite. Always uses --batch.

SERVERHercules MCP SOURCE0xmihirk/hercules-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xmihirk-hercules-mcp/sqlmap-run.md

WHAT IT DOES

What sqlmap_run does on Hercules MCP

AI agents invoke sqlmap_run to trigger actions in Hercules 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.

RISK

Why sqlmap_run is rated High

sqlmap is a penetration testing tool that executes SQL injection attacks against databases. This triggers external operations (database queries) whose effects depend entirely on arguments (target URL, injection point, payload strategy). The tool has no built-in guard rails and runs in 'batch mode' (--batch), indicating automated, non-interactive exploitation.

From the tool's definition Tool is named 'sqlmap_run' and described as 'Automated SQL injection suite.' The context indicates it runs industry-standard offensive security tools in a containerized Kali Linux environment.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sqlmap_run safely

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

sqlmap_run Rate-limited

sqlmap_run 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_run": {
      "limits": [
        {
          "counter": "sqlmap_run_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 Hercules MCP, apply this rule, and every sqlmap_run call is checked against it from then on.

FAQ

Questions about sqlmap_run

What does the sqlmap_run tool do? +

Automated SQL injection suite. Always uses --batch. It is categorised as a Execute tool in the Hercules 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_run? +

Register the Hercules MCP server in PolicyLayer and add a rule for sqlmap_run: 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 Hercules MCP. Nothing to install.

What risk level is sqlmap_run? +

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

Can I rate-limit sqlmap_run? +

Yes. Add a rate_limit block to the sqlmap_run 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_run completely? +

Set action: deny in the PolicyLayer policy for sqlmap_run. 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_run? +

sqlmap_run is provided by the Hercules MCP server (0xmihirk/hercules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hercules, and thousands of servers like it.

This server

All 45 Hercules tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →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 →