AI agents call grid_get_order_details 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 |
|---|---|---|---|
algoId | string | Yes | Grid bot algo order ID (not a trade ordId) |
algoOrdType | string | Yes | grid=Spot, contract_grid=Contract |
Parameters from the server's own tool schema.
This tool queries and retrieves existing grid bot details (configuration, status, profit/loss, position data) without modifying data, executing trades, or affecting financial state. It is a read-only information retrieval operation. The low severity reflects minimal blast radius even if misused by an agent, as it only exposes account information already known to the account holder.
From the tool's definition Tool name contains 'get' and description states 'Get grid bot detail by algo ID. Returns config, status, PnL, and position.' — purely retrieves information with no modification or execution capability.
Attacks that exploit this kind of access
Get grid bot detail by algo ID. Returns config, status, PnL, and position. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
grid_get_order_details accepts 2 parameters: algoId, 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_order_details: 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_order_details 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_order_details 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_order_details. 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_order_details 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 →