Create a futures grid order (openapi_bot.yaml CreateFuturesGridRequest / CreateFuturesGridOrderData). https://github.com/pionex-official/pionex-open-api/blob/main/openapi_bot.yaml — Required: base, quote, buOrderData. Optional: copyFrom, copyType, copyBotOrderId. buOrderData required: top, bottom...
AI agents use pionex_bot_futures_grid_create 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); *.PERP normalized in handler |
quote | string | Yes | Quote currency (e.g. USDT) |
__dryRun | boolean | — | Internal: when true, return resolved body without POST |
copyFrom | string | — | Optional. Copy source order ID |
copyType | string | — | Optional. Copy type |
buOrderData | object | Yes | CreateFuturesGridOrderData (openapi_bot.yaml). Required: top, bottom, row, grid_type, trend, leverage, quoteInvestment. |
copyBotOrderId | string | — | Optional. Copy bot order ID |
Parameters from the server's own tool schema.
This tool creates leveraged futures trading orders on Pionex, directly committing financial resources with leverage. Misuse could result in significant financial losses due to leveraged positions. It falls squarely in the Financial category as it places real trading orders with real money, and the leverage parameter amplifies the financial risk to critical severity.
From the tool's definition Create a futures grid order — initiates leveraged futures trading positions with financial commitment (quoteInvestment, leverage fields)
Risk signalsHigh parameter count (42 properties)
Attacks that exploit this kind of access
Create a futures grid order (openapi_bot.yaml CreateFuturesGridRequest / CreateFuturesGridOrderData). https://github.com/pionex-official/pionex-open-api/blob/main/openapi_bot.yaml — Required: base, quote, buOrderData. Optional: copyFrom, copyType, copyBotOrderId. buOrderData required: top, bottom, row, grid_type, trend, leverage, quoteInvestment; unknown keys rejected. 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_bot_futures_grid_create accepts 7 parameters: base, quote, __dryRun, copyFrom, copyType, buOrderData, copyBotOrderId. Required: base, quote, buOrderData. 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_bot_futures_grid_create: 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_bot_futures_grid_create 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_bot_futures_grid_create 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_bot_futures_grid_create. 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_bot_futures_grid_create 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 →