Query local audit log of tool calls made through this MCP server. Returns recent operations with timestamps, duration, params, and results. Use to review what trades or queries were executed in this session or past sessions.
AI agents call trade_get_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 |
|---|---|---|---|
tool | string | — | e.g. swap_place_order |
level | string | — | |
limit | number | — | Max results (default 20) |
since | string | — | ISO 8601 timestamp lower bound |
Parameters from the server's own tool schema.
This tool retrieves and displays historical audit log data from past operations. It does not execute trades, modify account settings, transfer funds, or delete records—it only reads and returns existing log entries. This is a pure Read operation with minimal risk, appropriate for reviewing transaction history or debugging purposes.
From the tool's definition Tool name is 'trade_get_history' and description states it 'Query[s] local audit log' and 'Returns recent operations with timestamps, duration, params, and results.' The verb is 'Query' and 'Returns', both retrieval operations with no modification or…
Attacks that exploit this kind of access
Query local audit log of tool calls made through this MCP server. Returns recent operations with timestamps, duration, params, and results. Use to review what trades or queries were executed in this session or past sessions. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
trade_get_history accepts 4 parameters: tool, level, limit, since. 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 trade_get_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.
trade_get_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 trade_get_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 trade_get_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.
trade_get_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 →