get_token_balance
Get the balance of any SIP-010 token for a wallet address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID: address.contract-name
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-token-balance.md
What get_token_balance does on Aibtc
AI agents call get_token_balance to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_token_balance is rated Low
This tool queries token balance information for a specified wallet and token, returning data without any side effects or ability to modify state. It falls clearly under Read category as a data retrieval operation. Severity is low because balance queries pose minimal risk even if misused by an agent—they only expose financial information visibility without enabling transfers or other actions.
From the tool's definition Tool description states 'Get the balance of any SIP-010 token for a wallet address' — a retrieval operation with no modification capability. The verb 'Get' and the data retrieval nature confirm this is a query-only function.
Attacks that exploit this kind of access
The rule that runs get_token_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_token_balance, this is the rule to start with:
get_token_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 Aibtc, apply this rule, and every get_token_balance call is checked against it from then on.
Questions about get_token_balance
Get the balance of any SIP-010 token for a wallet address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID: address.contract-name. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc 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 Aibtc. 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 Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue