AI agents call option_get_fills 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 |
|---|---|---|---|
end | string | — | End time (ms) |
after | string | — | Cursor: return older |
begin | string | — | Start time (ms) |
limit | number | — | Max results |
ordId | string | — | Order ID filter |
before | string | — | Cursor: return newer |
instId | string | — | Instrument filter |
archive | boolean | — | true=up to 3 months; false=last 3 days (default) |
Parameters from the server's own tool schema.
This tool queries historical transaction/fill data from the OKX exchange. It is a pure read operation that retrieves existing data without creating, modifying, deleting, or executing any operations. While it accesses financial trading history, the tool itself performs only data retrieval and poses minimal risk if misused by an AI agent—it cannot move funds, execute trades, or alter account state.
From the tool's definition Tool name is "option_get_fills" and description states it retrieves fill history data. The parameters (archive flag) only control the time range of historical data queried, not any modification or execution.
Attacks that exploit this kind of access
Get OPTION fill history. archive=false: last 3 days (default); archive=true: up to 3 months. It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
option_get_fills accepts 8 parameters: end, after, begin, limit, ordId, before, instId, archive. 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 option_get_fills: 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.
option_get_fills 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 option_get_fills 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 option_get_fills. 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.
option_get_fills 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 →