Get one futures grid bot order by buOrderId.
AI agents call pionex_bot_futures_grid_get_order 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 |
|---|---|---|---|
lang | string | — | Optional language code. |
buOrderId | string | Yes | Futures grid bot order id. |
Parameters from the server's own tool schema.
This tool retrieves information about a specific futures grid bot order using an order ID. The verb 'Get' and the read-only nature of querying order details classify it as a Read operation. While the broader server manages financial trading accounts and has access to credentials, this specific tool only retrieves data without creating, modifying, deleting, or executing trades.
From the tool's definition Tool name contains 'get_order' and description states 'Get one futures grid bot order by buOrderId' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get one futures grid bot order by buOrderId. 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_get_order accepts 2 parameters: lang, buOrderId. Required: buOrderId. 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_get_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_bot_futures_grid_get_order 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_get_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_bot_futures_grid_get_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_bot_futures_grid_get_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 →