solve_image
Solve an image captcha. Supports: local file path, base64 string, data-URI, or an HTML snippet with an <img> tag.
This record as markdown: /tools/2captcha/solve-image.md
What solve_image does on 2captcha
AI agents invoke solve_image 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_image is rated High
This tool submits a captcha to an external service for solving, constituting an external operation with side effects (consuming API credits, interacting with third-party infrastructure). It is not a simple read, and while it costs credits (minor financial aspect), the primary classification is Execute due to triggering external computation/service calls. Misuse could facilitate bypassing bot-detection at scale.
From the tool's definition "Solve an image captcha" — triggers an external CAPTCHA-solving operation via the 2Captcha service, processing input (file path, base64, data-URI, or HTML img tag) and invoking a third-party API
Attacks that exploit this kind of access
The rule that runs solve_image 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_image, this is the rule to start with:
solve_image 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_image call is checked against it from then on.
Questions about solve_image
Solve an image captcha. Supports: local file path, base64 string, data-URI, or an HTML snippet with an <img> tag. 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_image: 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_image 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_image 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_image. 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_image 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