# eth_getBalance

Retrieves the balance of a given Ethereum address

Agent View of the PolicyLayer registry record for `eth_getBalance`. HTML page: https://policylayer.com/tools/0xkoda-eth-mcp/eth-getbalance

## Facts

- Tool: `eth_getBalance`
- Server: Ethereum RPC MCP Server (`0xkoda/eth-mcp`) — https://policylayer.com/tools/0xkoda-eth-mcp.md
- Homepage: https://github.com/0xKoda/eth-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, 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": "eth_getBalance",
    "arguments": {}
  }
}
```

## Why eth_getBalance is rated Low

This tool only retrieves data about an Ethereum address balance without modifying, executing, deleting, or transferring any assets. It is a read-only operation analogous to checking an account balance, presenting minimal security risk even if misused by an AI agent.

From the tool's own definition: "Tool name 'eth_getBalance' and description 'Retrieves the balance of a given Ethereum address' indicate a query operation with no side effects."

## Use case

AI agents call eth_getBalance to retrieve information from Ethereum RPC 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 Ethereum RPC MCP Server:

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

## Other tools on Ethereum RPC MCP Server (2)

- `eth_gasPrice` — Read — https://policylayer.com/tools/0xkoda-eth-mcp/eth-gasprice.md
- `eth_getCode` — Read — https://policylayer.com/tools/0xkoda-eth-mcp/eth-getcode.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=0xkoda-eth-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xkoda-eth-mcp