# getTokensBalance

A read tool on the Ethereum Tools MCP server.

Agent View of the PolicyLayer registry record for `getTokensBalance`. HTML page: https://policylayer.com/tools/0xgval-evm-mcp-tools/gettokensbalance

## Facts

- Tool: `getTokensBalance`
- Server: Ethereum Tools (`0xgval/evm-mcp-tools`) — https://policylayer.com/tools/0xgval-evm-mcp-tools.md
- Homepage: https://github.com/0xGval/evm-mcp-tools
- 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": "getTokensBalance",
    "arguments": {}
  }
}
```

## Why getTokensBalance is rated Low

The 'get' prefix combined with 'Balance' strongly suggests this tool retrieves token balance information from the blockchain without modifying state. Although the description is empty, the naming pattern and server context (wallet analysis, on-chain data retrieval) indicate a read-only query operation. No side effects, no irreversible actions, no code execution, and no financial transactions are implied.

From the tool's own definition: "Tool name 'getTokensBalance' indicates a retrieval operation (get + query). Contextually, this is part of an Ethereum analysis toolkit focused on blockchain data retrieval."

## Use case

AI agents call getTokensBalance to retrieve information from Ethereum Tools 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 Ethereum Tools:

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

## Other tools on Ethereum Tools (10)

- `add` — Other — https://policylayer.com/tools/0xgval-evm-mcp-tools/add.md
- `analyzeToken` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/analyzetoken.md
- `auditContract` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/auditcontract.md
- `getEthBalance` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/getethbalance.md
- `getTokenInfo` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/gettokeninfo.md
- `getTokenPriceHistory` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/gettokenpricehistory.md
- `getTransactionCount` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/gettransactioncount.md
- `getWalletPnl` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/getwalletpnl.md
- `searchTwitter` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/searchtwitter.md
- `twitterSearchHelp` — Read — https://policylayer.com/tools/0xgval-evm-mcp-tools/twittersearchhelp.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=0xgval-evm-mcp-tools · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xgval-evm-mcp-tools