Batch query Dual Investment orders by client order IDs. Requires View permission (API key + secret).
AI agents call pionex_earn_dual_get_invests 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 | — | Base currency (e.g. BTC) |
clientDualIds | array | — | List of client-assigned dual investment order IDs to query. |
Parameters from the server's own tool schema.
This tool queries existing Dual Investment orders by ID, returning data without side effects. However, it accesses financial account data (Pionex trading account information), which elevates severity to medium due to potential sensitive information exposure (account holdings, investment status).
From the tool's definition Tool name contains 'get' and description explicitly states 'Batch query Dual Investment orders' — a retrieval operation with no modification. Requires 'View permission' confirming read-only access.
Attacks that exploit this kind of access
Batch query Dual Investment orders by client order IDs. 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_get_invests accepts 2 parameters: base, clientDualIds. 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_get_invests: 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_get_invests 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_get_invests 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_get_invests. 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_get_invests 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 →