grid_amend_order

Amend a running grid bot. [CAUTION] Modifies a running bot. Use grid_list_orders to confirm the bot is running and obtain the algoId before calling. Supports two modes, which can be combined in a single call: • Price-range mode (maxPx+minPx+gridNum): change upper/lower price boundary and grid cou...

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

What grid_amend_order does on Okx Trade

AI agents call grid_amend_order 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
maxPx string [Price-range mode] New upper price boundary. Triggers amend-algo-basic-param when provided.
minPx string [Price-range mode] New lower price boundary. Required when maxPx is set.
algoId string Yes Grid bot algo order ID (required)
instId string [TP/SL mode] Instrument ID, e.g. BTC-USDT. Required when setting TP/SL.
gridNum string [Price-range mode] New number of grid intervals (integer). Required when maxPx is set.
slRatio string [TP/SL mode] Stop-loss ratio, e.g. '0.1' = 10% drawdown. Pass '-1' to clear.
tpRatio string [TP/SL mode] Take-profit ratio, e.g. '0.1' = 10% profit. Pass '-1' to clear.
topUpAmt string Top-up amount. In price-range mode maps to topupAmount (contract grid only; omit to use minimum required). In TP/SL mode maps to topUpAmt.
slTriggerPx string [TP/SL mode] Stop-loss trigger price (absolute). Pass '-1' to clear.
tpTriggerPx string [TP/SL mode] Take-profit trigger price (absolute). Pass '-1' to clear.

Parameters from the server's own tool schema.

Why grid_amend_order needs a policy

An AI agent that decides to call grid_amend_order doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Okx Trade is gone — there is no undo for destructive operations.

Risk signalsHigh parameter count (10 properties)

Questions about grid_amend_order

What does the grid_amend_order tool do? +

Amend a running grid bot. [CAUTION] Modifies a running bot. Use grid_list_orders to confirm the bot is running and obtain the algoId before calling. Supports two modes, which can be combined in a single call: • Price-range mode (maxPx+minPx+gridNum): change upper/lower price boundary and grid count. Contract grid: if new range requires more margin, pass topUpAmt; omit to auto-use the minimum required. Spot grid: topUpAmt is not supported. • TP/SL mode (instId + any of tpTriggerPx/slTriggerPx/tpRatio/slRatio): update take-profit and/or stop-loss. Pass '-1' to explicitly clear an existing TP or SL. tpTriggerPx/slTriggerPx are absolute prices; tpRatio/slRatio are profit ratios (e.g. '0.1' = 10%). When both sets of params are provided, both APIs are called sequentially. Do NOT use to create a new grid bot - use grid_create_order instead. Do NOT use to stop a grid bot - use grid_stop_order instead. 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 grid_amend_order accept? +

grid_amend_order accepts 10 parameters: maxPx, minPx, algoId, instId, gridNum, slRatio, tpRatio, topUpAmt, slTriggerPx, tpTriggerPx. Required: algoId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on grid_amend_order? +

Register the Okx Trade MCP server in PolicyLayer and add a rule for grid_amend_order: 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 grid_amend_order? +

grid_amend_order 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 grid_amend_order? +

Yes. Add a rate_limit block to the grid_amend_order 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 grid_amend_order completely? +

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

grid_amend_order 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.