This record as markdown: /tools/2captcha/solve-turnstile.md
What solve_turnstile does on 2captcha
AI agents invoke solve_turnstile to trigger actions in 2captcha. 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.
Why solve_turnstile is rated High
The tool executes an external operation (submitting a CAPTCHA challenge to the 2Captcha service for solving), which has side effects: it consumes paid API credits and returns a bypass token. It is not a simple read, nor does it delete data or move money directly, but it does trigger a chargeable external action and can be used to circumvent security controls.
From the tool's definition 'solve_turnstile' — triggers an external CAPTCHA-solving operation against Cloudflare Turnstile, invoking a third-party service that consumes account credits and bypasses bot-detection mechanisms
Attacks that exploit this kind of access
The rule that runs solve_turnstile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 2captcha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For solve_turnstile, this is the rule to start with:
solve_turnstile 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 2captcha, apply this rule, and every solve_turnstile call is checked against it from then on.
Questions about solve_turnstile
Solve Cloudflare Turnstile. It is categorised as a Execute tool in the 2captcha MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 2captcha MCP server in PolicyLayer and add a rule for solve_turnstile: 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 2captcha. Nothing to install.
solve_turnstile 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 solve_turnstile 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 solve_turnstile. 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.
solve_turnstile is provided by the 2captcha MCP server (2captcha-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 2captcha, and thousands of servers like it.
Across the catalogue