Launch an AI-powered penetration test against a target URL. The target domain must be verified first — use turbopentest_list_domains to check. Requires an available credit matching the selected tier — use turbopentest_get_credits to check balance. Returns a pentest ID that can be used with turbop...
Part of the TurboPentest MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke turbopentest_start_scan to trigger processes or run actions in TurboPentest. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
turbopentest_start_scan can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
turbopentest_start_scan:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full TurboPentest policy for all 8 tools.
Agents calling execute-class tools like turbopentest_start_scan have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
turbopentest_start_scan is one of the high-risk operations in TurboPentest. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Launch an AI-powered penetration test against a target URL. The target domain must be verified first — use turbopentest_list_domains to check. Requires an available credit matching the selected tier — use turbopentest_get_credits to check balance. Returns a pentest ID that can be used with turbopentest_get_scan to monitor progress.. It is categorised as a Execute tool in the TurboPentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for turbopentest_start_scan. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the TurboPentest MCP server.
turbopentest_start_scan 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 turbopentest_start_scan 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_start_scan. 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_start_scan 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