# subscribeSpreadExecution

订阅 Spread 成交推送（需要鉴权）

Agent View of the PolicyLayer registry record for `subscribeSpreadExecution`. HTML page: https://policylayer.com/tools/bybit-exchange-trading-mcp/subscribespreadexecution

## Facts

- Tool: `subscribeSpreadExecution`
- Server: Bybit MCP Server (`bybit-exchange/trading-mcp`) — https://policylayer.com/tools/bybit-exchange-trading-mcp.md
- Homepage: https://github.com/bybit-exchange/trading-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "subscribeSpreadExecution",
    "arguments": {}
  }
}
```

## Why subscribeSpreadExecution is rated Low

The tool subscribes to a real-time data stream for spread execution events. Subscribing to a WebSocket feed is a read/monitoring operation with no side effects on orders, positions, or funds. The authentication requirement ('需要鉴权') is for access control, not because it modifies state. Severity is low since misuse only results in receiving market data.

From the tool's own definition: "订阅 Spread 成交推送 — 'subscribe' and '推送' (push/stream) indicate this is a data subscription for receiving spread execution updates"

## Use case

AI agents call subscribeSpreadExecution 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bybit MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "subscribeSpreadExecution": {}
  }
}
```

## Other tools on Bybit MCP Server (379)

- `batchCancelOrders` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/batchcancelorders.md
- `cancelAllOrders` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelallorders.md
- `cancelAllQuotes` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelallquotes.md
- `cancelAllRfqs` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelallrfqs.md
- `cancelAllSpreadOrders` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelallspreadorders.md
- `cancelOrder` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelorder.md
- `cancelRfq` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelrfq.md
- `cancelSpreadOrder` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/cancelspreadorder.md
- `closeComboBot` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/closecombobot.md
- `closeFGridBot` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/closefgridbot.md
- `closeFMartBot` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/closefmartbot.md
- `removeAd` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/removead.md
- `upgradeToUta` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/upgradetouta.md
- `wsBatchCancelOrders` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/wsbatchcancelorders.md
- `wsCancelOrder` — Destructive — https://policylayer.com/tools/bybit-exchange-trading-mcp/wscancelorder.md
- `acceptNonLpQuote` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/acceptnonlpquote.md
- `closeGridBot` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/closegridbot.md
- `confirmNewRiskLimit` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/confirmnewrisklimit.md
- `createComboBot` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/createcombobot.md
- `createTwapStrategy` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/createtwapstrategy.md
- `movePosition` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/moveposition.md
- `resetMmp` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/resetmmp.md
- `setTradingStop` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/settradingstop.md
- `stopStrategy` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/stopstrategy.md
- `stopSubscription` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/stopsubscription.md
- `wsAmendOrder` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/wsamendorder.md
- `wsBatchAmendOrders` — Execute — https://policylayer.com/tools/bybit-exchange-trading-mcp/wsbatchamendorders.md
- `accountBorrow` — Financial — https://policylayer.com/tools/bybit-exchange-trading-mcp/accountborrow.md
- `accountFixedBorrow` — Financial — https://policylayer.com/tools/bybit-exchange-trading-mcp/accountfixedborrow.md
- `accountNoConvertRepay` — Financial — https://policylayer.com/tools/bybit-exchange-trading-mcp/accountnoconvertrepay.md
- …and 349 more: https://policylayer.com/tools/bybit-exchange-trading-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=bybit-exchange-trading-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/bybit-exchange-trading-mcp