Validate spot grid bot parameters before creating an order. Uses the same buOrderData structure as spot_grid_create. On FailedWithData error the response includes min_investment, max_investment, slippage. Endpoint: POST /api/v1/bot/orders/spotGrid/checkParams
AI agents call pionex_bot_spot_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) |
quote | string | Yes | Quote currency (e.g. USDT) |
buOrderData | object | Yes | CreateSpotGridOrderData (openapi_bot.yaml PR #7). Required: top, bottom, row, gridType, quoteTotalInvestment. |
Parameters from the server's own tool schema.
This is a validation/query tool that checks parameters and returns constraints and validation results. It has no side effects—it does not create orders, execute trades, modify account state, or delete anything. The POST method is used for request body transmission rather than state modification. Classification as Read is appropriate for tools that perform validation checks and return informational responses.
From the tool's definition Tool description states 'Validate spot grid bot parameters before creating an order' and 'On FailedWithData error the response includes min_investment, max_investment, slippage.' The endpoint POST /api/v1/bot/orders/spotGrid/checkParams performs validation…
Risk signalsHigh parameter count (18 properties)
Attacks that exploit this kind of access
Validate spot grid bot parameters before creating an order. Uses the same buOrderData structure as spot_grid_create. On FailedWithData error the response includes min_investment, max_investment, slippage. Endpoint: POST /api/v1/bot/orders/spotGrid/checkParams. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_bot_spot_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_spot_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_spot_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_spot_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_spot_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_spot_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 →