Set API rate limit for specified UIDs under exchange broker account.\n\nRate limit: 1 req per second.\n\nRules:\n- Only exchange broker accounts can call this endpoint.\n- If the UID calling this endpoint is a master account, the UIDs specified in the
AI agents use setBrokerApiLimit to create or update resources in Bybit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.
This tool creates or modifies API rate limit configuration for specified UIDs, which is a Write operation (reversible administrative change). It affects multiple user accounts under a broker structure, making it high severity due to potential service disruption if misused (e.g., setting limits to 0 could block legitimate trading).
From the tool's definition "Set API rate limit for specified UIDs under exchange broker account" — modifies rate limit configuration for broker accounts, a reversible administrative setting.
Documented attack patterns abuse exactly the kind of access setBrokerApiLimit 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 setBrokerApiLimit:
{
"version": "1",
"default": "deny",
"tools": {
"setBrokerApiLimit": {
"limits": [
{
"counter": "setbrokerapilimit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} setBrokerApiLimit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set API rate limit for specified UIDs under exchange broker account.\n\nRate limit: 1 req per second.\n\nRules:\n- Only exchange broker accounts can call this endpoint.\n- If the UID calling this endpoint is a master account, the UIDs specified in the. It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for setBrokerApiLimit: 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.
setBrokerApiLimit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setBrokerApiLimit 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 setBrokerApiLimit. 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.
setBrokerApiLimit 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.