AI agents call get_small_balance_exchange_history to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical balance exchange records without side effects. It is a read-only operation that queries past data, fitting the Read category. Severity is low because exposure of historical balance data poses minimal risk compared to tools that modify orders or execute trades on the Bybit exchange.
From the tool's definition Tool name and description indicate data retrieval: 'get_small_balance_exchange_history' performs a query/fetch operation to retrieve historical exchange data. No modification, deletion, or execution of commands is described.
Attacks that exploit this kind of access
Get small balance exchange history. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_small_balance_exchange_history: 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. Nothing to install.
get_small_balance_exchange_history 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_small_balance_exchange_history 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_small_balance_exchange_history. 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_small_balance_exchange_history is provided by the Bybit MCP server (johnnywic/bybit-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 →