Collect settled Dual Investment earnings into the user's spot account. Requires Earn permission (API key + secret). Only orders in a settled state can be collected.
AI agents use pionex_earn_dual_collect to commit financial operations through Pionex Trade — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
base | string | Yes | Base currency (e.g. BTC) |
productId | string | Yes | Product ID (e.g. BTC-USDXO-260402-68000-P-USDT) |
clientDualId | string | Yes | Client-assigned dual investment order ID to collect |
Parameters from the server's own tool schema.
This tool moves funds (earnings) into the user's spot account, constituting a financial transaction. While it collects already-settled earnings rather than initiating new trades or payments, it directly affects the user's financial balances and account state. Misuse could result in unauthorized collection or timing issues with financial assets.
From the tool's definition Collect settled Dual Investment earnings into the user's spot account
Attacks that exploit this kind of access
Collect settled Dual Investment earnings into the user's spot account. Requires Earn permission (API key + secret). Only orders in a settled state can be collected. It is categorised as a Financial tool in the Pionex Trade MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
pionex_earn_dual_collect accepts 3 parameters: base, productId, clientDualId. Required: base, productId, clientDualId. 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_collect: 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_collect is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pionex_earn_dual_collect 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_collect. 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_collect 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 →