New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_leverage

Set leverage for a trading position. Higher leverage amplifies both profits and losses. Use with caution as it increases risk significantly.

SERVERBybit MCP Server SOURCEbcusack/bybit-py-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/bcusack-bybit-py-mcp/set-leverage.md

What set_leverage does on Bybit MCP Server

AI agents invoke set_leverage to trigger actions in Bybit MCP Server. 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.

Why set_leverage is rated High

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.'

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.

More on Bybit MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.