Close an existing position to realize PnL. Requires TRADEX_KEYPAIR to be configured.
AI agents use close_position to commit financial operations through TradeX MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Closing a futures position is a direct financial action that commits a trade, realizes gains or losses, and moves funds. It is irreversible once executed on-chain. This clearly falls under the Financial category, which takes precedence over all others.
From the tool's definition 'Close an existing position to realize PnL' — closes a live trading position on a perpetual futures market, executing a financial transaction that realizes profit or loss on the Solana blockchain using a configured keypair.
Attacks that exploit this kind of access
Close an existing position to realize PnL. Requires TRADEX_KEYPAIR to be configured. It is categorised as a Financial tool in the TradeX MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the TradeX MCP Server 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 TradeX MCP Server. 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 TradeX MCP Server MCP server (tradexcards/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →