Run vulnerability scanning (Nuclei + RouterSploit + nikto + dirb). De-duplicates against findings already in the engagement, filters false positives, scores by CVSS + EPSS exploit probability. Returns immediately with engagement_id; agent runs asynchronously.
AI agents invoke test_vulnerabilities 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.
This tool launches active security scanning tools (Nuclei, RouterSploit, nikto, dirb) against targets. These are real offensive/reconnaissance tools that make network requests, probe services, and attempt to identify exploitable vulnerabilities. This constitutes executing external operations with significant blast radius — scanning without authorization is illegal and could disrupt target systems.
From the tool's definition Run vulnerability scanning (Nuclei + RouterSploit + nikto + dirb) — actively executes multiple real security scanning tools against a target
Documented attack patterns abuse exactly the kind of access test_vulnerabilities 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 test_vulnerabilities:
{
"version": "1",
"default": "deny",
"tools": {
"test_vulnerabilities": {
"limits": [
{
"counter": "test_vulnerabilities_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test_vulnerabilities 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 vulnerability scanning (Nuclei + RouterSploit + nikto + dirb). De-duplicates against findings already in the engagement, filters false positives, scores by CVSS + EPSS exploit probability. Returns immediately with engagement_id; agent runs asynchronously. 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 test_vulnerabilities: 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.
test_vulnerabilities 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 test_vulnerabilities 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 test_vulnerabilities. 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.
test_vulnerabilities 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.