close_position
Market-close the open position on symbol. Returns None if no position.
This record as markdown: /tools/0xdegenmo-lighter-mcp/close-position.md
What close_position does on Lighter MCP
AI agents use close_position to commit financial operations through Lighter MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why close_position is rated Critical
This tool closes a trading position on a perpetual DEX, which is a financial operation that executes a market order to exit a position. This directly affects financial holdings and is irreversible once executed on-chain. Misuse could result in significant financial loss by closing positions at unfavorable market prices or closing positions unintentionally.
From the tool's definition Market-close the open position on `symbol`
Attacks that exploit this kind of access
The rule that runs close_position 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 close_position, this is the rule to start with:
Any call to close_position 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 close_position call is checked against it from then on.
Questions about close_position
Market-close the open position on symbol. Returns None if no position. 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 close_position: 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.
close_position 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 close_position 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 close_position. 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.
close_position 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