Set the maximum leverage for spot cross margin trading. Account must have spot margin activated first. Valid leverage range is 2 to 10.
AI agents use spotMarginSetLeverage 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 account trading parameters (leverage settings) reversibly through the Bybit API. While not destructive or financial in itself, setting leverage is a Write action that reconfigures account state and materially affects the risk profile of subsequent trades.
From the tool's definition Tool description states 'Set the maximum leverage for spot cross margin trading' — the word 'Set' indicates modification of account configuration. The leverage setting directly affects trading constraints and risk exposure on the account.
Documented attack patterns abuse exactly the kind of access spotMarginSetLeverage 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 spotMarginSetLeverage:
{
"version": "1",
"default": "deny",
"tools": {
"spotMarginSetLeverage": {
"limits": [
{
"counter": "spotmarginsetleverage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} spotMarginSetLeverage 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 maximum leverage for spot cross margin trading. Account must have spot margin activated first. Valid leverage range is 2 to 10. 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 spotMarginSetLeverage: 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.
spotMarginSetLeverage 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 spotMarginSetLeverage 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 spotMarginSetLeverage. 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.
spotMarginSetLeverage 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.