set_leverage
Set per-market leverage. Cross margin is the default.
This record as markdown: /tools/0xdegenmo-lighter-mcp/set-leverage.md
What set_leverage does on Lighter MCP
AI agents use set_leverage to create or update resources in Lighter MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lighter MCP environment.
Why set_leverage is rated Medium
set_leverage modifies trading parameters reversibly—leverage can be adjusted again. However, it operates in a financial context (perpetual derivatives trading) where leverage changes carry high operational risk: incorrect leverage settings can trigger liquidations, losses of collateral, or amplified drawdowns.
From the tool's definition Tool modifies leverage settings per-market on a perpetual DEX (Lighter). Description states it 'Set[s] per-market leverage', which is a configuration change that affects open positions and future trades.
Attacks that exploit this kind of access
The rule that runs set_leverage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lighter MCP, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Lighter MCP, apply this rule, and every set_leverage call is checked against it from then on.
Questions about set_leverage
Set per-market leverage. Cross margin is the default. It is categorised as a Write tool in the Lighter MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lighter 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 Lighter MCP. Nothing to install.
set_leverage 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 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.
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.
set_leverage is provided by the Lighter MCP server (0xdegenmo/lighter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lighter, and thousands of servers like it.
This server
Across the catalogue