AI agents call spot_get_orders 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | — | End time (ms) |
after | string | — | Cursor: older than this order ID |
begin | string | — | Start time (ms) |
limit | number | — | Max results (default 100) |
state | string | — | canceled|filled |
before | string | — | Cursor: newer than this order ID |
instId | string | — | Instrument ID filter |
status | string | — | |
ordType | string | — | Order type filter |
Parameters from the server's own tool schema.
This tool queries historical and current spot order data without side effects. It is a read-only operation that retrieves information about orders. While the OKX Trade server overall handles financial operations, this specific tool performs no writes, deletions, or financial movements—it only retrieves order status and history.
From the tool's definition Tool name 'spot_get_orders' and description 'Query spot orders' with status filters (open, history, archive) indicate data retrieval only. No creation, modification, deletion, or financial transaction execution.
Attacks that exploit this kind of access
Query spot orders. status: open(active)|history(7d)|archive(3mo). It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
spot_get_orders accepts 9 parameters: end, after, begin, limit, state, before, instId, status, ordType. The full parameter table on this page comes from the server's own tool schema.
Register the Okx Trade MCP server in PolicyLayer and add a rule for spot_get_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 Okx Trade. Nothing to install.
spot_get_orders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spot_get_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 spot_get_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.
spot_get_orders 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.
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 →