place_stop_loss
Place an on-chain stop-loss (reduce-only).
This record as markdown: /tools/0xdegenmo-lighter-mcp/place-stop-loss.md
What place_stop_loss does on Lighter MCP
AI agents use place_stop_loss to commit financial operations through Lighter MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why place_stop_loss is rated Critical
This tool places an on-chain financial order on a perpetual DEX. Stop-loss orders are financial instruments that automatically trigger trades/position closures when price thresholds are hit, directly committing financial obligations and affecting real assets on-chain. Misuse could result in unintended liquidation of positions or financial losses.
From the tool's definition Place an on-chain stop-loss (reduce-only)
Attacks that exploit this kind of access
The rule that runs place_stop_loss 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 place_stop_loss, this is the rule to start with:
Any call to place_stop_loss is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Lighter MCP, apply this rule, and every place_stop_loss call is checked against it from then on.
Questions about place_stop_loss
Place an on-chain stop-loss (reduce-only). It is categorised as a Financial tool in the Lighter MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lighter MCP server in PolicyLayer and add a rule for place_stop_loss: 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.
place_stop_loss is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the place_stop_loss 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 place_stop_loss. 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.
place_stop_loss 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.
Across the catalogue