option_batch_cancel

[CAUTION] Batch cancel up to 20 OPTION orders.

Server Okx Trade @okx_ai/okx-trade-mcp
Category Destructive
Risk class Critical
Parameters 11 required

What option_batch_cancel does on Okx Trade

AI agents call option_batch_cancel to permanently remove resources in Okx Trade — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
orders array Yes Array (max 20): {instId, ordId?, clOrdId?}

Parameters from the server's own tool schema.

Why option_batch_cancel needs a policy

Cancelling orders is an irreversible action — once cancelled, the orders cannot be reinstated. The batch nature (up to 20 at once) amplifies the blast radius. While it doesn't move money directly, it destroys active trading positions/intentions in a way that cannot be undone, placing it firmly in the Destructive category. The [CAUTION] tag from the server authors reinforces the elevated risk.

From the tool's definition 'Batch cancel up to 20 OPTION orders' and the '[CAUTION]' warning flag indicate irreversible cancellation of multiple financial orders

Questions about option_batch_cancel

What does the option_batch_cancel tool do? +

[CAUTION] Batch cancel up to 20 OPTION orders. It is categorised as a Destructive tool in the Okx Trade MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does option_batch_cancel accept? +

option_batch_cancel accepts 1 parameter: orders. Required: orders. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on option_batch_cancel? +

Register the Okx Trade MCP server in PolicyLayer and add a rule for option_batch_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 Okx Trade. Nothing to install.

What risk level is option_batch_cancel? +

option_batch_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit option_batch_cancel? +

Yes. Add a rate_limit block to the option_batch_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.

How do I block option_batch_cancel completely? +

Set action: deny in the PolicyLayer policy for option_batch_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.

What MCP server provides option_batch_cancel? +

option_batch_cancel is provided by the Okx Trade MCP server (@okx_ai/okx-trade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.