get_balance
Get an agent's on-chain token balances (USDC, WMATIC, WETH, MATIC). No api_key required.
This record as markdown: /tools/io-github-wirternow-agent-bank/get-balance.md
What get_balance does on Ai Agent Bank
AI agents call get_balance to retrieve information from Ai Agent Bank without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | string | Yes | UUID of the agent |
Parameters from the server's own tool schema.
Why get_balance is rated Low
This tool retrieves financial data (token balances) but does not create, modify, delete, or move funds. It has no side effects and presents minimal risk even if called by an AI agent, as it only exposes already-public blockchain information. The low severity reflects that balance information leakage alone cannot cause financial harm.
From the tool's definition Tool description states 'Get an agent's on-chain token balances' which is a retrieval operation that queries blockchain state without modification. The phrase 'No api_key required' further indicates read-only access.
Attacks that exploit this kind of access
The rule that runs get_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ai Agent Bank, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_balance, this is the rule to start with:
get_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ai Agent Bank, apply this rule, and every get_balance call is checked against it from then on.
Questions about get_balance
Get an agent's on-chain token balances (USDC, WMATIC, WETH, MATIC). No api_key required. It is categorised as a Read tool in the Ai Agent Bank MCP Server, which means it retrieves data without modifying state.
get_balance accepts 1 parameter: agent_id. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Agent Bank MCP server in PolicyLayer and add a rule for get_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 Ai Agent Bank. Nothing to install.
get_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_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_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_balance is provided by the Ai Agent Bank MCP server (https://tdueqhfxyojmjgactdyc.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ai Agent Bank, and thousands of servers like it.
This server
Across the catalogue