place_take_profit
Place an on-chain take-profit (reduce-only). Same semantics as SL.
This record as markdown: /tools/0xdegenmo-lighter-mcp/place-take-profit.md
What place_take_profit does on Lighter MCP
AI agents use place_take_profit 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_take_profit is rated Critical
This tool places a financial order on a perpetual DEX (decentralized exchange). It creates on-chain trading orders that can directly affect open positions and financial outcomes. Even though it's reduce-only (closing existing positions rather than opening new ones), it commits financial transactions on-chain that trigger real monetary settlements.
From the tool's definition Place an on-chain take-profit (reduce-only)
Attacks that exploit this kind of access
The rule that runs place_take_profit 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_take_profit, this is the rule to start with:
Any call to place_take_profit 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_take_profit call is checked against it from then on.
Questions about place_take_profit
Place an on-chain take-profit (reduce-only). Same semantics as SL. 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_take_profit: 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_take_profit 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_take_profit 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_take_profit. 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_take_profit 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