Set the leverage for a contract position. Supports linear and inverse contracts.\nIn one-way mode or cross margin mode, buyLeverage and sellLeverage must be equal.\nIn isolated margin hedge mode, they can differ.\n\nAgent hint: Use this to change leverage on an existing or new position. Always se...
AI agents use setLeverage to create or update resources in Bybit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.
This tool modifies the leverage setting on a trading position. While it doesn't directly move money, changing leverage on a cryptocurrency derivatives position is a high-impact financial configuration change that significantly affects risk exposure and potential liquidation price.
From the tool's definition Set the leverage for a contract position... change leverage on an existing or new position. Always set both buyLeverage and sellLeverage.
Documented attack patterns abuse exactly the kind of access setLeverage gives an agent:
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 setLeverage:
{
"version": "1",
"default": "deny",
"tools": {
"setLeverage": {
"limits": [
{
"counter": "setleverage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setLeverage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the leverage for a contract position. Supports linear and inverse contracts.\nIn one-way mode or cross margin mode, buyLeverage and sellLeverage must be equal.\nIn isolated margin hedge mode, they can differ.\n\nAgent hint: Use this to change leverage on an existing or new position. Always set both buyLeverage and sellLeverage.\nFor one-way mode and cross margin, they must be identical. Do not set leverage to the current value or it will error. It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for setLeverage: 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.
setLeverage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setLeverage 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.
Set action: deny in the PolicyLayer policy for setLeverage. 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.
setLeverage is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.