set_leverage

THE RISK

High Risk

Why set_leverage needs a policy

Setting leverage modifies the risk parameters of an active or future trading position on a financial exchange. While it doesn't directly move money, it changes how positions are margined and can cause liquidations, making it a high-severity Execute action that triggers an external operation on Bybit's trading infrastructure.

From the tool's definition 'Set leverage for a trading position. Higher leverage amplifies both profits and losses. Use with caution as it increases risk significantly.'

Documented attack patterns abuse exactly the kind of access set_leverage gives an agent:

POLICY

How to control set_leverage

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 set_leverage:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_leverage": {
      "limits": [
        {
          "counter": "set_leverage_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

set_leverage stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Bybit MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bybit MCP Server tools

Financial place_order Place a new trading order on Bybit. ⚠️ EXECUTES REAL TRADES WITH REAL MONEY when trading i Financial place_trigger_order Place a conditional/trigger order that executes only when market price reaches your trigge Financial batch_place_order Place multiple orders in a single request. More efficient than placing orders individually Financial batch_amend_order Modify multiple existing orders in a single request. More efficient than amending orders i Financial set_trading_stop Set take profit and stop loss orders for an existing position. These orders automatically Destructive batch_cancel_order Cancel multiple existing orders in a single request. More efficient than canceling orders Destructive cancel_all_orders Cancel all pending orders for a category or specific symbol. Use with caution as this canc Destructive cancel_order Cancel a single pending order immediately. ⚠️ Only works on orders that haven

All 36 Bybit MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
High-risk tools in Bybit MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about set_leverage

What does the set_leverage tool do? +

Set leverage for a trading position. Higher leverage amplifies both profits and losses. Use with caution as it increases risk significantly. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_leverage? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for set_leverage: 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.

What risk level is set_leverage? +

set_leverage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_leverage? +

Yes. Add a rate_limit block to the set_leverage 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.

How do I block set_leverage completely? +

Set action: deny in the PolicyLayer policy for set_leverage. 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.

What MCP server provides set_leverage? +

set_leverage is provided by the Bybit MCP Server MCP server (bcusack/bybit-py-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bybit MCP Server tool call.

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.

CHECK YOUR STACK →