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...
AI agents call getRpiOrderbook 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 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.
Documented attack patterns abuse exactly the kind of access getRpiOrderbook 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 getRpiOrderbook:
{
"version": "1",
"default": "deny",
"tools": {
"getRpiOrderbook": {}
}
}getRpiOrderbook 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.
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.
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.