getComboDetail
Retrieves comprehensive details for a specific futures combo bot, including\nconfiguration (symbols, leverage, rebalancing mode), current display status,\nPnL metrics (total PnL, realized, unrealized, funding fee), portfolio position\ninfo, margin balances (total, available, margin balance), and ...
This record as markdown: /tools/bybit-exchange-trading-mcp/getcombodetail.md
What getComboDetail does on Bybit MCP Server
AI agents call getComboDetail 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 getComboDetail is rated Low
This tool only queries and returns data about an existing combo bot—its configuration, performance metrics, and account balances. It does not modify state, execute trades, delete data, or commit financial transactions.
From the tool's definition Retrieves comprehensive details for a specific futures combo bot, including configuration, current display status, PnL metrics, portfolio position info, margin balances, and timestamps.
Attacks that exploit this kind of access
The rule that runs getComboDetail 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 getComboDetail, this is the rule to start with:
getComboDetail 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 getComboDetail call is checked against it from then on.
Questions about getComboDetail
Retrieves comprehensive details for a specific futures combo bot, including\nconfiguration (symbols, leverage, rebalancing mode), current display status,\nPnL metrics (total PnL, realized, unrealized, funding fee), portfolio position\ninfo, margin balances (total, available, margin balance), and timestamps.\n\nThe bot_id is a numeric ID obtained from createComboBot or bot listing endpoints.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Use this endpoint to check the status and performance of a combo bot.\nThe response contains all PnL fields, position details, rebalancing stats,\nand close reason if the bot has stopped. Prefer this over other endpoints\nwhen answering questions about a specific bot. 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 getComboDetail: 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.
getComboDetail 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 getComboDetail 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 getComboDetail. 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.
getComboDetail 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