AI agents call spot_get_algo_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 |
|---|---|---|---|
after | string | — | Cursor: older than this algo ID |
limit | number | — | Max results (default 100) |
state | string | — | Required for history. effective=triggered, canceled, order_failed. Default: effective. |
before | string | — | Cursor: newer than this algo ID |
instId | string | — | Instrument ID filter |
status | string | — | pending=active (default), history=completed |
ordType | string | — | Filter by type |
Parameters from the server's own tool schema.
This tool retrieves information about algorithmic trading orders (take-profit/stop-loss) from the OKX exchange. It has no side effects—it only reads and returns order data. While it is part of a trading platform, querying order history or pending orders does not move money, execute trades, or modify any state. It is a pure read operation and poses minimal risk of unintended consequences if called by an AI agent.
From the tool's definition Tool name is 'spot_get_algo_orders' and description states 'Query spot algo orders' which indicates data retrieval. The phrase 'pending or history' confirms this queries existing orders without modification or execution.
Attacks that exploit this kind of access
Query spot algo orders (TP/SL) - pending or history. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
spot_get_algo_orders accepts 7 parameters: after, 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_algo_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_algo_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_algo_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_algo_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_algo_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 →