Retrieve structured vulnerability findings for a completed penetration test. Each finding includes severity, CVSS score, CWE classification, detailed description, proof of concept, remediation steps, and a retest command. Returns up to 20 findings at a time — use the severity filter to focus on s...
Part of the TurboPentest MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call turbopentest_get_findings to retrieve information from TurboPentest without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though turbopentest_get_findings only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
turbopentest_get_findings:
rules:
- action: allowSee the full TurboPentest policy for all 8 tools.
Agents calling read-class tools like turbopentest_get_findings have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieve structured vulnerability findings for a completed penetration test. Each finding includes severity, CVSS score, CWE classification, detailed description, proof of concept, remediation steps, and a retest command. Returns up to 20 findings at a time — use the severity filter to focus on specific risk levels. Use turbopentest_download_report for a complete exportable report.. It is categorised as a Read tool in the TurboPentest MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for turbopentest_get_findings. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the TurboPentest MCP server.
turbopentest_get_findings 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 turbopentest_get_findings rule in your Intercept 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 Intercept policy for turbopentest_get_findings. 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.
turbopentest_get_findings is provided by the TurboPentest MCP server (integsec/turbopentest). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept