queryBrokerEarning
Use exchange broker master account to query earnings and rebate information.\n\nRate limit: 10 req per second.\n\nRules:\n- The data can support up to past 1 month until T-1. To extract data from over a month ago, please contact your Relationship Manager.\n-
This record as markdown: /tools/bybit-exchange-trading-mcp/querybrokerearning.md
What queryBrokerEarning does on Bybit MCP Server
AI agents call queryBrokerEarning 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 queryBrokerEarning is rated Low
This tool performs a read-only query of broker earnings and rebate data from a master account. It has no side effects, does not modify data, execute commands, or move money. While it exposes financial information that could be sensitive, the core function is passive data retrieval.
From the tool's definition Tool name is 'queryBrokerEarning' and description states 'query earnings and rebate information' — retrieves historical financial data without modification or execution.
Attacks that exploit this kind of access
The rule that runs queryBrokerEarning 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 queryBrokerEarning, this is the rule to start with:
queryBrokerEarning 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 queryBrokerEarning call is checked against it from then on.
Questions about queryBrokerEarning
Use exchange broker master account to query earnings and rebate information.\n\nRate limit: 10 req per second.\n\nRules:\n- The data can support up to past 1 month until T-1. To extract data from over a month ago, please contact your Relationship Manager.\n-. 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 queryBrokerEarning: 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.
queryBrokerEarning 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 queryBrokerEarning 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 queryBrokerEarning. 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.
queryBrokerEarning 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