Run a specific security tool against a target. Returns structured results that are automatically stored in the findings database.
AI agents invoke run_tool to trigger actions in Pentest Ai. 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.
While framed as a 'security tool' in a pentest context, this tool executes external security utilities with user-controlled parameters (target selection). Security tools can perform reconnaissance, exploitation, or destructive actions depending on arguments. The tool doesn't inherently restrict to read-only operations; security tools like Metasploit, sqlmap, or custom exploits could be invoked.
From the tool's definition Tool description explicitly states 'Run a specific security tool against a target' — this is a direct execution action. The ability to run arbitrary security tools with configurable targets creates substantial blast radius for misuse.
Documented attack patterns abuse exactly the kind of access run_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for run_tool:
{
"version": "1",
"default": "deny",
"tools": {
"run_tool": {
"limits": [
{
"counter": "run_tool_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_tool 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.
Free to start. No card required.
Run a specific security tool against a target. Returns structured results that are automatically stored in the findings database. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for run_tool: 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 Pentest Ai. Nothing to install.
run_tool 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_tool 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_tool. 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_tool is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.