close_all_positions
Close all open positions at market price.
This record as markdown: /tools/luiinventions-bitunix-mcp/close-all-positions.md
What close_all_positions does on Bitunix MCP
AI agents use close_all_positions to commit financial operations through Bitunix MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why close_all_positions is rated Critical
This tool immediately closes all open trading positions at market price, which is a high-severity financial action. It commits irreversible financial transactions across potentially many positions simultaneously, locking in gains or losses with no ability to undo the trades. Misuse by an AI agent could result in catastrophic financial loss.
From the tool's definition Close all open positions at market price
Attacks that exploit this kind of access
The rule that runs close_all_positions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitunix MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_all_positions, this is the rule to start with:
Any call to close_all_positions is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitunix MCP, apply this rule, and every close_all_positions call is checked against it from then on.
Questions about close_all_positions
Close all open positions at market price. It is categorised as a Financial tool in the Bitunix MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitunix MCP server in PolicyLayer and add a rule for close_all_positions: 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 Bitunix MCP. Nothing to install.
close_all_positions 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_all_positions 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_all_positions. 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_all_positions is provided by the Bitunix MCP server (luiinventions/bitunix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bitunix, and thousands of servers like it.
Across the catalogue