AI agents call grid_get_sub_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 |
|---|---|---|---|
type | string | — | filled=executed trades (default); live=pending |
after | string | — | Cursor for older records |
limit | number | — | Default 100 |
algoId | string | Yes | Grid bot algo order ID (not a trade ordId) |
before | string | — | Cursor for newer records |
groupId | string | — | A buy-sell pair shares the same groupId |
algoOrdType | string | Yes | grid=Spot, contract_grid=Contract |
Parameters from the server's own tool schema.
This is a read-only query operation that retrieves historical or current order data from grid trading bots. No financial transactions, executions, or modifications occur. While it provides market/position information on a financial exchange, the tool itself performs no write, execute, or financial action—it only inspects existing data.
From the tool's definition Tool name 'grid_get_sub_orders' and description 'Query sub-orders' indicate a retrieval operation. The description explicitly states it queries existing bot orders without modifying or executing trades—it only retrieves state ('filled' for executed; 'live'…
Attacks that exploit this kind of access
Query sub-orders (grid trades) of a bot. type='filled' for executed; 'live' for pending. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
grid_get_sub_orders accepts 7 parameters: type, after, limit, algoId, before, groupId, algoOrdType. Required: algoId, algoOrdType. 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 grid_get_sub_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.
grid_get_sub_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 grid_get_sub_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 grid_get_sub_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.
grid_get_sub_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 →