Check ALGO and tUSDC balance for an address. Defaults to the active session wallet if address is omitted.
AI agents call get_balance to retrieve information from Question Market without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of blockchain account balances. It has no side effects, does not create, modify, or delete data, does not execute code or transactions, and does not involve financial movements. The default behavior of using the active session wallet does not change the classification since the operation remains non-destructive.
From the tool's definition Tool name 'get_balance' and description 'Check ALGO and tUSDC balance for an address' indicate a query operation that retrieves account balance information without modifying data or executing code.
Attacks that exploit this kind of access
Check ALGO and tUSDC balance for an address. Defaults to the active session wallet if address is omitted. It is categorised as a Read tool in the Question Market MCP Server, which means it retrieves data without modifying state.
Register the Question Market 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 Question Market. 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 Question Market MCP server (qmrkt/mcp-server). 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 →