AI agents invoke browser_solve_captcha to trigger actions in MCProxy. 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.
This tool executes an action in a headless browser by submitting a CAPTCHA solution, which triggers an external operation (bypassing bot-detection mechanisms on remote websites). It doesn't merely read data—it actively interacts with and manipulates a web session's state.
From the tool's definition Submit a CAPTCHA solution... analyze the screenshot from browser_check_captcha or browser_navigate, then provide the solution text here
Attacks that exploit this kind of access
Submit a CAPTCHA solution. For image CAPTCHAs, analyze the screenshot from browser_check_captcha or browser_navigate, then provide the solution text here. It is categorised as a Execute tool in the MCProxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCProxy MCP server in PolicyLayer and add a rule for browser_solve_captcha: 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 MCProxy. Nothing to install.
browser_solve_captcha 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 browser_solve_captcha 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 browser_solve_captcha. 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.
browser_solve_captcha is provided by the MCProxy MCP server (saladtechnologies/mcproxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →