queryBrokerCap

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/querybrokercap.md

WHAT IT DOES

What queryBrokerCap does on Bybit MCP Server

AI agents call queryBrokerCap 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.

RISK

Why queryBrokerCap is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs queryBrokerCap 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 queryBrokerCap, this is the rule to start with:

queryBrokerCap Allowed

queryBrokerCap is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "queryBrokerCap": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every queryBrokerCap call is checked against it from then on.

FAQ

Questions about queryBrokerCap

What does the queryBrokerCap tool do? +

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.

How do I enforce a policy on queryBrokerCap? +

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.

What risk level is queryBrokerCap? +

queryBrokerCap is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit queryBrokerCap? +

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.

How do I block queryBrokerCap completely? +

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.

What MCP server provides queryBrokerCap? +

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.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →