Running sqlmap on a target.
AI agents invoke run_sqlmap to trigger actions in Hacking Buddy 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.
This tool executes sqlmap, an automated SQL injection testing framework that runs potentially destructive database attacks on a target system. While the actual impact (Read, Write, or Destructive) depends on target vulnerability and sqlmap arguments, the tool's purpose is to execute external security testing code whose effects are not guaranteed to be reversible. This makes it Execute rather than Read.
From the tool's definition Tool name is 'run_sqlmap' and description states 'Running sqlmap on a target.' SQLmap is a command-line tool that executes SQL injection attacks and penetration tests against databases. The 'run_' prefix indicates execution of an external operation.
Attacks that exploit this kind of access
Running sqlmap on a target. It is categorised as a Execute tool in the Hacking Buddy MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hacking Buddy MCP server in PolicyLayer and add a rule for run_sqlmap: 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 Hacking Buddy MCP. Nothing to install.
run_sqlmap 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 run_sqlmap 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 run_sqlmap. 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.
run_sqlmap is provided by the Hacking Buddy MCP server (manuelberrueta/hacking-buddy-mcp). 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 →