AI agents invoke sqlmap_scan to trigger actions in Kali. 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.
SQLMap does far more than passively read; it actively probes and exploits SQL injection flaws, potentially exfiltrating entire databases, bypassing authentication, or gaining OS-level access. On a Kali Linux penetration-testing server alongside Hydra and Metasploit, the blast radius if misused against unauthorized targets is critical — it constitutes unauthorized access and data theft.
From the tool's definition 'Use SQLMap to test for SQL injection vulnerabilities' — SQLMap is an active exploitation tool that sends crafted payloads to target systems, can extract databases, dump data, and in advanced modes execute OS commands or write files
Attacks that exploit this kind of access
Use SQLMap to test for SQL injection vulnerabilities. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali 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. Nothing to install.
sqlmap_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
sqlmap_scan is provided by the Kali MCP server (rangta10/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →