queryBalance
Query fiat or crypto account balances.\n\nQuery Parameters:\n- accountCategory: Account type (fiat/crypto), defaults to fiat\n- currency: Currency code, omit to return all balances\n\nBalance Information:\n- totalBalance: Total balance\n- balance: Available balance\n- frozenBalance: Frozen (locke...
This record as markdown: /tools/bybit-exchange-trading-mcp/querybalance.md
What queryBalance does on Bybit MCP Server
AI agents call queryBalance to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why queryBalance is rated Low
This tool only queries and returns balance information without creating, modifying, deleting, or executing operations. It has no side effects on account state. The low severity reflects minimal blast radius: an AI agent misusing this tool can at worst retrieve balance data, which does not expose financial risk or enable unauthorized transactions.
From the tool's definition Tool name is 'queryBalance' and description states it 'Query[s] fiat or crypto account balances' with use cases limited to 'Display available balance', 'Validate sufficient funds', and 'Show detailed balance breakdown' — all read-only operations that retrieve…
Attacks that exploit this kind of access
The rule that runs queryBalance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For queryBalance, this is the rule to start with:
queryBalance 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 Bybit MCP Server, apply this rule, and every queryBalance call is checked against it from then on.
Questions about queryBalance
Query fiat or crypto account balances.\n\nQuery Parameters:\n- accountCategory: Account type (fiat/crypto), defaults to fiat\n- currency: Currency code, omit to return all balances\n\nBalance Information:\n- totalBalance: Total balance\n- balance: Available balance\n- frozenBalance: Frozen (locked) balance\n\nUse Cases:\n- Display available balance before trading\n- Validate sufficient funds before quote application\n- Show detailed balance breakdown to users. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for queryBalance: 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 Bybit MCP Server. Nothing to install.
queryBalance 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 queryBalance 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 queryBalance. 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.
queryBalance is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
This server
Across the catalogue