Cancel and close a futures grid bot order.
AI agents call pionex_bot_futures_grid_cancel to permanently remove resources in Pionex Trade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
buOrderId | string | Yes | |
closeNote | string | — | |
immediate | boolean | — | |
closeSlippage | string | — | |
closeSellModel | string | — |
Parameters from the server's own tool schema.
Canceling an active futures grid bot order permanently closes the trading position and ceases all associated trading activity. This is irreversible: once canceled, the bot stops executing, and any pending orders are removed. In the context of financial trading, this destroys the active state of a financial instrument position.
From the tool's definition 'Cancel and close a futures grid bot order' - this action irreversibly terminates an active futures trading position, which cannot be undone.
Attacks that exploit this kind of access
Cancel and close a futures grid bot order. It is categorised as a Destructive tool in the Pionex Trade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
pionex_bot_futures_grid_cancel accepts 5 parameters: buOrderId, closeNote, immediate, closeSlippage, closeSellModel. Required: buOrderId. The full parameter table on this page comes from the server's own tool schema.
Register the Pionex Trade MCP server in PolicyLayer and add a rule for pionex_bot_futures_grid_cancel: 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 Pionex Trade. Nothing to install.
pionex_bot_futures_grid_cancel is a Destructive 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 pionex_bot_futures_grid_cancel 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 pionex_bot_futures_grid_cancel. 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.
pionex_bot_futures_grid_cancel is provided by the Pionex Trade MCP server (@pionex/pionex-trade-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 →