AI agents call option_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: return older |
limit | number | — | Max results (default 100) |
state | string | — | When history: effective|canceled|order_failed |
algoId | string | — | Filter by algo order ID |
before | string | — | Cursor: return newer |
instId | string | — | Instrument ID filter |
status | string | — | pending=active (default); history=completed |
ordType | string | — | Filter by type; omit for all |
Parameters from the server's own tool schema.
This is a read-only query tool that retrieves historical and current order data. However, given the financial context (OKX exchange, options trading) and that order details could inform or be misused in subsequent financial decisions, severity is elevated to 'medium' rather than 'low'. The tool itself does not move money, execute trades, or modify state.
From the tool's definition Tool name includes 'get' and description states 'Query pending or completed OPTION algo orders' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Query pending or completed OPTION algo orders (TP/SL, OCO). It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
option_get_algo_orders accepts 8 parameters: after, limit, state, algoId, 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 option_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.
option_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 option_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 option_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.
option_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 →