# get_balance

Check your 2Captcha account balance.

Agent View of the PolicyLayer registry record for `get_balance`. HTML page: https://policylayer.com/tools/2captcha/get-balance

## Facts

- Tool: `get_balance`
- 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: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why get_balance is rated Low

The tool only retrieves the current balance from the user's 2Captcha account. It does not modify, delete, or move funds—it simply queries and returns data. This is a straightforward Read operation with minimal risk. Severity is low because even if exposed to an AI agent, the worst outcome is information disclosure of the account balance, which has limited blast radius.

From the tool's own definition: "Tool name is 'get_balance' and description states 'Check your 2Captcha account balance.' This is a read-only query operation that retrieves account information with no side effects."

## Use case

AI agents call get_balance to retrieve information from 2captcha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_balance": {}
  }
}
```

## Other tools on 2captcha (7)

- `solve_hcaptcha` — Execute — https://policylayer.com/tools/2captcha/solve-hcaptcha.md
- `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
- `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