Get filled trades (fills) for a symbol in a time range. Requires API key. Returns up to 100 latest fills.
AI agents call pionex_orders_get_fills to retrieve information from Pionex 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 |
|---|---|---|---|
symbol | string | Yes | e.g. BTC_USDT |
endTime | integer | — | End time in milliseconds. |
startTime | integer | — | Start time in milliseconds. |
Parameters from the server's own tool schema.
This tool queries and retrieves filled trade data for a given symbol within a time range. It has no side effects: it does not create, modify, delete, or execute trades. While the tool requires API credentials (indicating access to sensitive financial data), the action itself is purely informational retrieval.
From the tool's definition Tool description states 'Get filled trades (fills)' and 'Returns up to 100 latest fills' — these are read operations that retrieve historical transaction data without modifying or executing trades.
Attacks that exploit this kind of access
Get filled trades (fills) for a symbol in a time range. Requires API key. Returns up to 100 latest fills. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_orders_get_fills accepts 3 parameters: symbol, endTime, startTime. Required: symbol. The full parameter table on this page comes from the server's own tool schema.
Register the Pionex Trade MCP server in PolicyLayer and add a rule for pionex_orders_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 Pionex Trade. Nothing to install.
pionex_orders_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 pionex_orders_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 pionex_orders_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.
pionex_orders_get_fills is provided by the Pionex Trade MCP server (@pionex/pionex-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 →