Create a spot order on Pionex. LIMIT requires symbol/side/type=LIMIT/price/size. MARKET BUY requires amount (quote). MARKET SELL requires size (base).
AI agents use pionex_orders_new_order 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 |
|---|---|---|---|
IOC | boolean | — | Immediate-or-cancel, default false |
side | string | Yes | |
size | string | — | Quantity; required for limit and market sell |
type | string | Yes | |
price | string | — | Required for limit order |
amount | string | — | Quote amount; required for market buy |
symbol | string | Yes | e.g. BTC_USDT |
clientOrderId | string | — | Optional client order id (max 64 chars) |
Parameters from the server's own tool schema.
This tool directly executes financial trades on a live exchange, committing real monetary obligations. Misuse could result in unintended purchases or sales of assets at any price or size, making it Financial category with critical severity due to potential for significant monetary loss.
From the tool's definition 'Create a spot order on Pionex' — explicitly places financial market orders (LIMIT, MARKET BUY, MARKET SELL) involving real currency amounts
Attacks that exploit this kind of access
Create a spot order on Pionex. LIMIT requires symbol/side/type=LIMIT/price/size. MARKET BUY requires amount (quote). MARKET SELL requires size (base). 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_orders_new_order accepts 8 parameters: IOC, side, size, type, price, amount, symbol, clientOrderId. Required: side, type, 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_new_order: 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_new_order 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_orders_new_order 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_new_order. 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_new_order 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 →