AI agents call account_get_positions_history 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 | — | 1=close long,2=close short,3=liq long,4=liq short,5=ADL long,6=ADL short |
after | string | — | Pagination: before this timestamp (ms) |
limit | number | — | Max results (default 20) |
posId | string | — | |
before | string | — | Pagination: after this timestamp (ms) |
instId | string | — | e.g. BTC-USDT-SWAP |
mgnMode | string | — | |
instType | string | — | Default SWAP |
Parameters from the server's own tool schema.
This tool retrieves historical data about closed positions without creating, modifying, deleting, or executing trades. It is purely informational. While the OKX Trade server context involves financial instruments, this specific tool performs read-only queries and does not move money, commit financial obligations, or execute trades.
From the tool's definition Tool name includes 'get' and description states 'Get closed position history' — a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get closed position history for SWAP or FUTURES. Default 20 records, max 100. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
account_get_positions_history accepts 8 parameters: type, after, limit, posId, before, instId, mgnMode, instType. 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 account_get_positions_history: 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.
account_get_positions_history 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 account_get_positions_history 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 account_get_positions_history. 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.
account_get_positions_history 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 →