Use the master account to query for all your UID-level rate limits, including all master accounts and subaccounts.\n\nRate limit: 1 req per second.\n\nRules:\n- Only exchange broker accounts can call this endpoint.\n- Accounts that have never had a rate limit configured via Set Rate Limit will no...
AI agents call queryBrokerAllUidDetails 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 rate limit configuration information for broker accounts and subaccounts. It performs a read-only query operation with no side effects—it neither modifies account state, executes trades, moves funds, nor deletes data. The blast radius of misuse is minimal; an attacker gains visibility into rate limit settings but cannot directly harm the account through this tool alone.
From the tool's definition Tool name 'queryBrokerAllUidDetails' and description 'query for all your UID-level rate limits' indicates retrieval of existing configuration data with no modification, deletion, or execution of trades/commands.
Documented attack patterns abuse exactly the kind of access queryBrokerAllUidDetails 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 queryBrokerAllUidDetails:
{
"version": "1",
"default": "deny",
"tools": {
"queryBrokerAllUidDetails": {}
}
}queryBrokerAllUidDetails 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.
Use the master account to query for all your UID-level rate limits, including all master accounts and subaccounts.\n\nRate limit: 1 req per second.\n\nRules:\n- Only exchange broker accounts can call this endpoint.\n- Accounts that have never had a rate limit configured via Set Rate Limit will not appear in the response and will use the default rate limit. 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 queryBrokerAllUidDetails: 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.
queryBrokerAllUidDetails 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 queryBrokerAllUidDetails 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 queryBrokerAllUidDetails. 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.
queryBrokerAllUidDetails 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.