# three_balance

Return the $THREE and SOL balance for a Solana pubkey. If no pubkey is given, uses the configured signer (SOLANA_SECRET_KEY). Read-only — no payment.

Agent View of the PolicyLayer registry record for `three_balance`. HTML page: https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-balance

## Facts

- Tool: `three_balance`
- Server: $THREE Token (`@three-ws/three-token-mcp`) — https://policylayer.com/tools/io-github-nirholas-three-token-mcp.md
- Install: `npx -y @three-ws/three-token-mcp`
- Homepage: https://github.com/nirholas/three.ws
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `pubkey` | string | no | Base58 pubkey to read. Defaults to the configured signer's address. |

Parameters from the server's own tool schema.

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

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

## Why three_balance is rated Low

This tool queries blockchain state to retrieve token and SOL balances for a given Solana public key. It performs no writes, executions, deletions, or financial transactions. The explicit 'Read-only' designation and absence of payment mechanisms confirm this is a data retrieval operation with no side effects.

From the tool's own definition: "Tool description explicitly states 'Return the $THREE and SOL balance' and 'Read-only — no payment.' The tool retrieves balance data without modifying state or executing side effects."

## Use case

AI agents call three_balance to retrieve information from $THREE Token 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 $THREE Token:

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

## Other tools on $THREE Token (2)

- `three_burn` — Destructive — https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-burn.md
- `three_price` — Read — https://policylayer.com/tools/io-github-nirholas-three-token-mcp/three-price.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=io-github-nirholas-three-token-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-nirholas-three-token-mcp