AI agents call spot_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: older than this bill ID |
begin | string | — | Start time (ms) |
limit | number | — | Max results (default 100 or 20 for archive) |
ordId | string | — | Order ID filter |
before | string | — | Cursor: newer than this bill ID |
instId | string | — | Instrument ID filter |
archive | boolean | — | true=up to 3mo, false=3d (default) |
Parameters from the server's own tool schema.
This tool retrieves historical transaction data for spot trading fills. It is a pure query operation with no capability to create, modify, delete, or execute trades. Even in the context of a financial exchange, retrieval of past transaction history poses minimal risk and falls squarely into the Read category. The 'archive' parameter only controls which historical dataset is accessed, not any state-changing operation.
From the tool's definition Tool name 'spot_get_fills' and description 'Get spot transaction fills' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get spot transaction fills. archive=false(3d, default)|true(up to 3mo). It is categorised as a Read tool in the Okx Trade MCP Server, which means it retrieves data without modifying state.
spot_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 spot_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.
spot_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 spot_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 spot_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.
spot_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 →