# solve_hcaptcha

A execute tool on the 2captcha MCP server.

Agent View of the PolicyLayer registry record for `solve_hcaptcha`. HTML page: https://policylayer.com/tools/2captcha/solve-hcaptcha

## Facts

- Tool: `solve_hcaptcha`
- Server: 2captcha (`2captcha-mcp`) — https://policylayer.com/tools/2captcha.md
- Install: `npx -y 2captcha-mcp`
- Homepage: https://www.npmjs.com/package/2captcha-mcp
- Risk category: Execute (High risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "solve_hcaptcha",
    "arguments": {}
  }
}
```

## Why solve_hcaptcha is rated High

Solving a captcha is an external operation with side effects: it consumes paid credits (financial adjacency) and enables bypassing of security controls. It is best classified as Execute because it triggers an external service operation. Severity is high because automated captcha solving at scale enables abuse, scraping, or account takeover attacks.

From the tool's own definition: "solve_hcaptcha – 'Solve hCaptcha' triggers an external captcha-solving operation via the 2Captcha service, consuming API credits and bypassing bot-detection mechanisms"

## Use case

AI agents invoke solve_hcaptcha 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 2captcha:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "solve_hcaptcha": {
      "limits": [
        {
          "counter": "solve_hcaptcha_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 2captcha (7)

- `solve_image` — Execute — https://policylayer.com/tools/2captcha/solve-image.md
- `solve_recaptcha_v2` — Execute — https://policylayer.com/tools/2captcha/solve-recaptcha-v2.md
- `solve_turnstile` — Execute — https://policylayer.com/tools/2captcha/solve-turnstile.md
- `get_balance` — Read — https://policylayer.com/tools/2captcha/get-balance.md
- `report_incorrect` — Read — https://policylayer.com/tools/2captcha/report-incorrect.md
- `solve_arkose` — Read — https://policylayer.com/tools/2captcha/solve-arkose.md
- `solve_geetest` — Read — https://policylayer.com/tools/2captcha/solve-geetest.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2captcha · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2captcha