AI agents call check_sqlmap_status to retrieve information from pentestMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive status-check tool that only reads/polls information about an ongoing scan. It does not execute new penetration testing actions, modify data, or destroy anything. While the server hosts offensive security tools, this specific tool is a read-only monitoring utility. The 'low' severity reflects that misuse would only expose scan progress information rather than launch attacks or compromise systems.
From the tool's definition Tool name 'check_sqlmap_status' and description 'Non-blocking status check' indicates a query operation that retrieves the current state of a running SQLMap scan without modifying, executing new scans, or affecting target systems.
Documented attack patterns abuse exactly the kind of access check_sqlmap_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and pentestMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for check_sqlmap_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_sqlmap_status": {}
}
}check_sqlmap_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Non-blocking status check for SQLMap scan:. It is categorised as a Read tool in the pentestMCP MCP Server, which means it retrieves data without modifying state.
Register the pentest MCP server in PolicyLayer and add a rule for check_sqlmap_status: 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 pentestMCP. Nothing to install.
check_sqlmap_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_sqlmap_status 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 check_sqlmap_status. 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.
check_sqlmap_status is provided by the pentest MCP server (ramkansal/pentestmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 pentestMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 pentestMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.