Get the balance of a specific token for a specific address
AI agents call get_token_balance to retrieve information from Etherscan MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries token balance information from a blockchain. It has no side effects—it does not create, modify, delete, or execute any operations. It is purely informational, similar to the sibling tools (get_chain_id, get_filtered_rpc_list, get_token_holders, get_token_holders_count, get_total_supply), which are all Read operations.
From the tool's definition Tool name 'get_token_balance' and description 'Get the balance of a specific token for a specific address' indicate a query operation that retrieves blockchain data without modification or execution of code.
Attacks that exploit this kind of access
Get the balance of a specific token for a specific address. It is categorised as a Read tool in the Etherscan MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Etherscan MCP Tool MCP server in PolicyLayer and add a rule for get_token_balance: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Etherscan MCP Tool. Nothing to install.
get_token_balance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_token_balance rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_token_balance. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_token_balance is provided by the Etherscan MCP Tool MCP server (septemhill/etherscan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →