getRpiOrderbook
Retrieve orderbook depth data that explicitly shows RPI (Retail Price Improvement) order sizes\nat each price level, alongside regular non-RPI order sizes.\n\nUse this endpoint when you need to:\n- Identify the RPI liquidity available at each price level separately from non-RPI liquidity\n- Disti...
This record as markdown: /tools/bybit-exchange-trading-mcp/getrpiorderbook.md
What getRpiOrderbook does on Bybit MCP Server
AI agents call getRpiOrderbook 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 getRpiOrderbook is rated Low
This tool queries and retrieves market data (orderbook depth information with RPI order sizes) without creating, modifying, deleting, or executing any state-changing operations. It is a passive data retrieval endpoint for market microstructure analysis.
From the tool's definition Tool description explicitly states 'Retrieve orderbook depth data' and 'Access the full orderbook including RPI orders'. The verb 'Retrieve' and the stated purpose of accessing/identifying liquidity data without modification indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs getRpiOrderbook 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 getRpiOrderbook, this is the rule to start with:
getRpiOrderbook 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 getRpiOrderbook call is checked against it from then on.
Questions about getRpiOrderbook
Retrieve orderbook depth data that explicitly shows RPI (Retail Price Improvement) order sizes\nat each price level, alongside regular non-RPI order sizes.\n\nUse this endpoint when you need to:\n- Identify the RPI liquidity available at each price level separately from non-RPI liquidity\n- Distinguish between RPI and non-RPI order flow for market microstructure analysis\n- Access the full orderbook including RPI orders (which are excluded from the standard orderbook)\n\nSupported Products: Spot, USDT contract, Inverse contract\n\nEach price level returns a 3-element array:. 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 getRpiOrderbook: 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.
getRpiOrderbook 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 getRpiOrderbook 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 getRpiOrderbook. 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.
getRpiOrderbook 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