Get your exchange broker account entity total rate limit usage and cap, across the board.\n\nRate limit: 5 req per second.\n\nRules:\n- Only Main UIDs can query this endpoint.\n- Only exchange broker accounts can call this endpoint.\n- If you never applied for a specific config via account manage...
AI agents call queryBrokerCap to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account-level rate limit and cap information for broker accounts. It performs a read-only query ('Get') without creating, modifying, deleting, executing code, or moving funds. The restrictions (Main UIDs, exchange broker accounts only) are access controls, not indicators of write or destructive capabilities.
From the tool's definition Tool name 'queryBrokerCap' and description 'Get your exchange broker account entity total rate limit usage and cap' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access queryBrokerCap gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for queryBrokerCap:
{
"version": "1",
"default": "deny",
"tools": {
"queryBrokerCap": {}
}
}queryBrokerCap is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get your exchange broker account entity total rate limit usage and cap, across the board.\n\nRate limit: 5 req per second.\n\nRules:\n- Only Main UIDs can query this endpoint.\n- Only exchange broker accounts can call this endpoint.\n- If you never applied for a specific config via account manager, the response will be empty. 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 queryBrokerCap: 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.
queryBrokerCap 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 queryBrokerCap 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 queryBrokerCap. 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.
queryBrokerCap 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.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.