spot_get_order

Get details of a single spot order.

Server Okx Trade @okx_ai/okx-trade-mcp
Category Read
Risk class Low
Parameters 31 required

What spot_get_order does on Okx Trade

AI agents call spot_get_order to retrieve information from Okx Trade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
ordId string Provide ordId or clOrdId
instId string Yes e.g. BTC-USDT
clOrdId string Provide ordId or clOrdId

Parameters from the server's own tool schema.

Why spot_get_order needs a policy

This tool queries order information from the OKX exchange without modifying, deleting, or executing trades. It is a read-only operation that retrieves existing order details. While it operates in a financial context, the tool itself performs no financial transactions, fund movements, or irreversible changes.

From the tool's definition Tool name 'spot_get_order' and description 'Get details of a single spot order' indicate a retrieval operation with no side effects.

Questions about spot_get_order

What does the spot_get_order tool do? +

Get details of a single spot order. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.

What parameters does spot_get_order accept? +

spot_get_order accepts 3 parameters: ordId, instId, clOrdId. Required: instId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on spot_get_order? +

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

spot_get_order is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spot_get_order? +

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

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

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