Cancel all open orders for a symbol.
AI agents call pionex_orders_cancel_all_orders 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 |
|---|---|---|---|
symbol | string | Yes | e.g. BTC_USDT |
Parameters from the server's own tool schema.
This tool meets the Destructive category definition: it irreversibly cancels/removes data (all open orders) that cannot be recovered once executed. While it could be classified as Execute (triggering an external operation), Destructive is more severe and more accurately reflects the nature of the action—bulk cancellation of orders is a point-of-no-return operation in financial trading.
From the tool's definition The tool description explicitly states it will 'Cancel all open orders for a symbol.' This irreversibly terminates all active trading orders without the ability to undo the action after execution.
Attacks that exploit this kind of access
Cancel all open orders for a symbol. 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_orders_cancel_all_orders accepts 1 parameter: symbol. Required: symbol. 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_orders_cancel_all_orders: 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_orders_cancel_all_orders 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_orders_cancel_all_orders 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_orders_cancel_all_orders. 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_orders_cancel_all_orders 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 →