Get historical settlement delivery prices for a Dual Investment pair. base is required; quote is optional but recommended to narrow results. Use USDXO for BTC/ETH pairs; use USDT for all other base currencies. The delivery price is the index price recorded at expiry, used to determine the settlem...
AI agents call pionex_earn_dual_delivery_prices 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, XRP) |
quote | string | — | Quote currency filter. Use USDXO for BTC/ETH pairs; use USDT for all other base currencies. |
endTime | integer | — | End timestamp in milliseconds |
startTime | integer | — | Start timestamp in milliseconds |
Parameters from the server's own tool schema.
This tool retrieves historical pricing data for informational purposes. It performs no writes, deletions, code execution, or financial transactions. The data is already settled (historical), so retrieving it has no side effects. Low severity because unauthorized access to historical prices poses minimal risk—this is typically public market data used for analysis only.
From the tool's definition Tool description explicitly states 'Get historical settlement delivery prices' and 'No authentication required.' The verb 'get' and action of retrieving historical data without modification indicate a read-only operation.
Attacks that exploit this kind of access
Get historical settlement delivery prices for a Dual Investment pair. base is required; quote is optional but recommended to narrow results. Use USDXO for BTC/ETH pairs; use USDT for all other base currencies. The delivery price is the index price recorded at expiry, used to determine the settlement direction. No authentication required. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_earn_dual_delivery_prices accepts 4 parameters: base, quote, endTime, startTime. Required: base. 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_delivery_prices: 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_delivery_prices 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_delivery_prices 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_delivery_prices. 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_delivery_prices 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 →