Validate a specific finding with a safe, non-destructive proof of concept. Confirms the vulnerability is real and exploitable without causing damage. Runs asynchronously (PoC execution can take 30-120s); returns immediately with status='running'. Once complete, the finding's poc_status flips to '...
AI agents invoke validate_finding 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.
Despite being described as 'safe' and 'non-destructive', this tool actively executes proof-of-concept exploit code against a target to confirm real vulnerabilities are exploitable. This is an Execute-category action with high severity because it runs actual attack payloads against systems, and misuse (e.g., wrong target) could cause unintended harm.
From the tool's definition 'Validate a specific finding with a safe, non-destructive proof of concept' and 'Runs asynchronously (PoC execution can take 30-120s)' — executes exploit/PoC code against a target system
Documented attack patterns abuse exactly the kind of access validate_finding 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 validate_finding:
{
"version": "1",
"default": "deny",
"tools": {
"validate_finding": {
"limits": [
{
"counter": "validate_finding_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}validate_finding 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.
Validate a specific finding with a safe, non-destructive proof of concept. Confirms the vulnerability is real and exploitable without causing damage. Runs asynchronously (PoC execution can take 30-120s); returns immediately with status='running'. Once complete, the finding's poc_status flips to 'confirmed' or 'failed' — pull the updated finding via get_findings to read it. 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 validate_finding: 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.
validate_finding 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 validate_finding 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 validate_finding. 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.
validate_finding 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.