Get paginated Dual Investment history for the authenticated user. Requires View permission (API key + secret).
AI agents call pionex_earn_dual_records 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 |
|---|---|---|---|
base | string | Yes | Base currency (e.g. BTC) |
limit | integer | — | Maximum number of records per page (e.g. 20) |
quote | string | — | Quote currency filter. Use USDXO for BTC/ETH; use USDT for others. |
filter | string | — | Status filter |
endTime | integer | Yes | End timestamp in milliseconds (required) |
currency | string | — | Investment currency filter (e.g. USDT, BTC) |
startTime | integer | — | Start timestamp in milliseconds |
Parameters from the server's own tool schema.
This tool retrieves historical financial data about the authenticated user's Dual Investment positions. While it accesses sensitive financial information, it performs no mutations, deletions, or financial transactions. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool description explicitly states 'Get paginated Dual Investment history' - a retrieval operation with no side effects. The emphasis on 'Requires View permission' further confirms read-only access.
Attacks that exploit this kind of access
Get paginated Dual Investment history for the authenticated user. Requires View permission (API key + secret). It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_earn_dual_records accepts 7 parameters: base, limit, quote, filter, endTime, currency, startTime. Required: base, endTime. 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_earn_dual_records: 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_earn_dual_records 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_earn_dual_records 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_earn_dual_records. 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_earn_dual_records 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 →