getComboLimit
Validates the input parameters for creating a futures combo bot and returns\nthe allowable ranges for each parameter (initial margin, leverage, rebalancing\nthreshold, time interval, TP/SL percentages, trailing stop).\n\nUse this endpoint before calling /v5/fcombobot/create to\nensure parameters ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getcombolimit.md
What getComboLimit does on Bybit MCP Server
AI agents call getComboLimit 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 getComboLimit is rated Low
getComboLimit performs input validation and returns parameter constraints. It does not create, modify, delete, execute, or commit any financial transaction. It only reads and validates data from the API without any irreversible state changes. This is a preparatory read operation before other actions, making it a Read-category tool with low severity.
From the tool's definition Tool description states it 'Validates the input parameters' and 'returns the allowable ranges for each parameter.' The description explicitly instructs to 'Call this endpoint first to get valid parameter ranges before creating a combo bot.' This is a pure…
Attacks that exploit this kind of access
The rule that runs getComboLimit 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 getComboLimit, this is the rule to start with:
getComboLimit 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 getComboLimit call is checked against it from then on.
Questions about getComboLimit
Validates the input parameters for creating a futures combo bot and returns\nthe allowable ranges for each parameter (initial margin, leverage, rebalancing\nthreshold, time interval, TP/SL percentages, trailing stop).\n\nUse this endpoint before calling /v5/fcombobot/create to\nensure parameters are within valid bounds. The response includes a check_code\nthat indicates which parameter is out of range if validation fails.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Call this endpoint first to get valid parameter ranges before creating a combo bot.\nIf check_code is non-zero, the specific validation error is indicated by the code value.\nThe response ranges (init_margin, leverage, sl_percent, tp_percent, etc.) tell you\nthe exact min/max values allowed for each parameter. 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 getComboLimit: 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.
getComboLimit 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 getComboLimit 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 getComboLimit. 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.
getComboLimit 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