# get_balance

Get balance for a specific exchange account.

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

## Facts

- Tool: `get_balance`
- Server: :GT Protocol MCP Server (`gt-protocol/mcp`) — https://policylayer.com/tools/gt-protocol-mcp.md
- Homepage: https://github.com/gt-protocol/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, 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

This tool retrieves account balance information from exchange accounts (Binance/Hyperliquid) without side effects. It is purely informational—no funds are moved, no trades executed, no data modified or deleted. While the context involves financial accounts, the tool itself only reads balances; it does not commit financial obligations or move money, so it does not qualify as 'Financial' category.

From the tool's own definition: "Tool name 'get_balance' and description 'Get balance for a specific exchange account' indicate a read-only query operation that retrieves financial data without modification, deletion, or execution of transactions."

## Use case

AI agents call get_balance to retrieve information from :GT Protocol MCP Server 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 :GT Protocol MCP Server:

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

## Other tools on :GT Protocol MCP Server (18)

- `delete_bot` — Destructive — https://policylayer.com/tools/gt-protocol-mcp/delete-bot.md
- `run_backtest` — Execute — https://policylayer.com/tools/gt-protocol-mcp/run-backtest.md
- `start_bot` — Execute — https://policylayer.com/tools/gt-protocol-mcp/start-bot.md
- `stop_bot` — Execute — https://policylayer.com/tools/gt-protocol-mcp/stop-bot.md
- `close_deal` — Financial — https://policylayer.com/tools/gt-protocol-mcp/close-deal.md
- `start_deal` — Financial — https://policylayer.com/tools/gt-protocol-mcp/start-deal.md
- `authenticate` — Read — https://policylayer.com/tools/gt-protocol-mcp/authenticate.md
- `get_active_deals` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-active-deals.md
- `get_bot` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-bot.md
- `get_deal_history` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-deal-history.md
- `get_exchanges` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-exchanges.md
- `get_profile` — Read — https://policylayer.com/tools/gt-protocol-mcp/get-profile.md
- `list_bots` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-bots.md
- `list_deals` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-deals.md
- `list_portfolios` — Read — https://policylayer.com/tools/gt-protocol-mcp/list-portfolios.md
- `create_bot` — Write — https://policylayer.com/tools/gt-protocol-mcp/create-bot.md
- `paper_clone` — Write — https://policylayer.com/tools/gt-protocol-mcp/paper-clone.md
- `update_bot` — Write — https://policylayer.com/tools/gt-protocol-mcp/update-bot.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=gt-protocol-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/gt-protocol-mcp