AI agents call grid_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 |
|---|---|---|---|
after | string | — | Cursor for older records |
limit | number | — | Default 100 |
algoId | string | — | Grid bot algo order ID (not a trade ordId) |
before | string | — | Cursor for newer records |
instId | string | — | e.g. BTC-USDT, BTC-USD-SWAP |
status | string | — | active=running (default); history=stopped |
algoOrdType | string | Yes | grid=Spot, contract_grid=Contract |
Parameters from the server's own tool schema.
This tool retrieves information about existing grid bot orders without creating, modifying, deleting, or executing any trades. It is purely informational, examining the state of grid bots rather than changing it. While the server context is financial trading, this specific tool only reads data and carries minimal risk if misused by an AI agent.
From the tool's definition Tool name 'grid_get_orders' and description 'List grid bots' indicate a query/retrieval operation with no side effects. The ability to filter by status ('active' or 'history') confirms this is a read-only list operation.
Attacks that exploit this kind of access
List grid bots. status='active' for running; 'history' for stopped. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
grid_get_orders accepts 7 parameters: after, limit, algoId, before, instId, status, algoOrdType. Required: 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_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_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_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_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_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 →