set_leverage

A execute tool on the Bybit MCP server.

SERVERBybit SOURCEjohnnywic/bybit-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/johnnywic-bybit-mcp/set-leverage.md

WHAT IT DOES

What set_leverage does on Bybit

AI agents invoke set_leverage to trigger actions in Bybit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why set_leverage is rated High

On a trading exchange like Bybit, 'set_leverage' changes the leverage multiplier for a trading position. This is a configuration change that affects trading risk and exposure. It doesn't directly move money but can dramatically amplify losses/gains on subsequent trades.

From the tool's definition Tool name 'set_leverage' on a trading exchange MCP server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_leverage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_leverage, this is the rule to start with:

set_leverage Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every set_leverage call is checked against it from then on.

FAQ

Questions about set_leverage

What does the set_leverage tool do? +

set_leverage is a execute tool on the Bybit MCP server. It is categorised as a Execute tool in the Bybit 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 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. 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 (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit, and thousands of servers like it.

This server

All 245 Bybit tools → High-risk tools on this server →

Across the catalogue

set_breakpoint on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →