Retrieve spread orderbook depth data for a specific spread combination symbol.\nReturns a snapshot of bid and ask price levels, along with sequence and timestamp\nfields for correlation with WebSocket streams.\n\nUse this endpoint when you need to:\n- Inspect current bid/ask depth before placing ...
AI agents call getSpreadOrderbook 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 only queries and retrieves market data from the Bybit exchange without creating, modifying, deleting, or executing any transactions. It is a read-only data retrieval operation with no side effects. Even though it operates on a financial exchange, it performs no financial transactions or state changes, keeping severity low.
From the tool's definition Tool retrieves 'spread orderbook depth data' and returns 'a snapshot of bid and ask price levels' with no modification of data. The description explicitly states 'Inspect current bid/ask depth' and 'Fetch' operations, which are read-only queries.
Documented attack patterns abuse exactly the kind of access getSpreadOrderbook 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 getSpreadOrderbook:
{
"version": "1",
"default": "deny",
"tools": {
"getSpreadOrderbook": {}
}
}getSpreadOrderbook 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 spread orderbook depth data for a specific spread combination symbol.\nReturns a snapshot of bid and ask price levels, along with sequence and timestamp\nfields for correlation with WebSocket streams.\n\nUse this endpoint when you need to:\n- Inspect current bid/ask depth before placing a spread order\n- Fetch the best bid/ask price and available size at each level\n- Correlate with the WebSocket orderbook stream using the. 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 getSpreadOrderbook: 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.
getSpreadOrderbook 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 getSpreadOrderbook 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 getSpreadOrderbook. 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.
getSpreadOrderbook 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.