// SCAN REPORT

Bybit Ws

7 tools. 1 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 6 Jul 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 06/07/2026

How to control Bybit Ws ↓

TOOL MAP

What Bybit Ws exposes to your agents

Read (6) Write / Execute (0) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Bybit Ws tools

Financial · Critical place_entry This tool directly places trading orders on Bybit, committing real financial transactions.

1 of Bybit Ws's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Bybit Ws

PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit Ws, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "place_entry": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "get_journal": {
    "limits": [
      {
        "counter": "get_journal_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Bybit Ws — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BYBIT WS →

Instant setup, no code required.

FULL CATALOGUE

All 7 Bybit Ws tools

FINANCIAL 1 tools

Financial place_entry Place a market or limit order to enter a LONG or SHORT position with SL/TP

READ 6 tools

Read get_journal Get trading journal analysis: FIFO-matched roundtrips, win rate, profit/loss ratio, disposition effect, overtr Read get_metrics Get daily trading metrics: SL/TP counts, entries, auto-entry stats Read get_positions Get current trading positions with unrealized PnL, stop-losses, and leverage Read get_risk_status Get risk limits and current usage: daily PnL vs max_daily_loss, margin vs max_total_margin, entry blocked stat Read scan_market Scan market for Bollinger Grid signals (LONG/SHORT candidates with scores) Read vpn_status Get VPN health: service status, traffic rates, connected clients

FAQ

Questions about Bybit Ws

Can an AI agent move money through the Bybit Ws MCP server? +

Yes. The Bybit Ws server exposes 1 financial tools including place_entry. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the Bybit Ws MCP server expose? +

7 tools across 1 categories: Read. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Bybit Ws? +

Register the Bybit Ws MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Bybit Ws tool call.

Deterministic rules across all 7 Bybit Ws tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BYBIT WS →

Instant setup, no code required.

7 Bybit Ws tools catalogued and risk-classified — across an index of 43,000+ MCP servers.