Validate futures grid bot parameters before creating an order. Uses the same buOrderData structure as futures_grid_create. On FailedWithData error the response includes min_investment, max_investment, slippage. Endpoint: POST /api/v1/bot/orders/futuresGrid/checkParams
AI agents call pionex_bot_futures_grid_check_params 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); *.PERP normalized in handler |
quote | string | Yes | Quote currency (e.g. USDT) |
buOrderData | object | Yes | CreateFuturesGridOrderData (openapi_bot.yaml). Required: top, bottom, row, grid_type, trend, leverage, quoteInvestment. |
Parameters from the server's own tool schema.
This is a validation/check tool that retrieves parameter constraints and validation results. Although it uses POST, it has no side effects—it does not create orders, modify account state, or commit financial transactions. It merely queries and returns validation data to inform decision-making before an order is created. This is a read operation with low blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Validate[s] futures grid bot parameters before creating an order' and 'response includes min_investment, max_investment, slippage'.
Risk signalsHigh parameter count (38 properties)
Attacks that exploit this kind of access
Validate futures grid bot parameters before creating an order. Uses the same buOrderData structure as futures_grid_create. On FailedWithData error the response includes min_investment, max_investment, slippage. Endpoint: POST /api/v1/bot/orders/futuresGrid/checkParams. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_bot_futures_grid_check_params accepts 3 parameters: base, quote, buOrderData. 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_check_params: 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_check_params 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_bot_futures_grid_check_params 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_check_params. 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_check_params 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 →