This record as markdown: /tools/bybit-exchange-trading-mcp/subscribespreadorder.md
What subscribeSpreadOrder does on Bybit MCP Server
AI agents call subscribeSpreadOrder 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 subscribeSpreadOrder is rated Low
The tool subscribes to a WebSocket stream for spread order changes, which is a read/monitoring operation. It does not place, modify, or cancel orders. The authentication requirement ('需要鉴权') is because it accesses private account data, not because it performs writes. Severity is low as it only reads streaming data.
From the tool's definition 订阅 Spread 订单变动 — 'subscribe' indicates listening/streaming to order change events
Attacks that exploit this kind of access
The rule that runs subscribeSpreadOrder 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 subscribeSpreadOrder, this is the rule to start with:
subscribeSpreadOrder 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 subscribeSpreadOrder call is checked against it from then on.
Questions about subscribeSpreadOrder
订阅 Spread 订单变动(需要鉴权). 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 subscribeSpreadOrder: 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.
subscribeSpreadOrder 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 subscribeSpreadOrder 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 subscribeSpreadOrder. 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.
subscribeSpreadOrder 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