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 server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"turbopentest_start_scan": {
"limits": [
{
"counter": "turbopentest_start_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} See the full TurboPentest policy for all 8 tools.
These attack patterns abuse exactly the kind of access turbopentest_start_scan gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the TurboPentest MCP server in PolicyLayer and add a rule for turbopentest_start_scan: 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 TurboPentest. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 TurboPentest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.