List bot orders with optional filters and pagination. status: 'running' (default) or 'finished'. buOrderTypes: one or more of futures_grid, spot_grid, smart_copy. Endpoint: GET /api/v1/bot/orders
AI agents call pionex_bot_order_list 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 | — | Base currency filter (e.g. BTC). |
quote | string | — | Quote currency filter (e.g. USDT). |
status | string | — | Filter by order status. Default: 'running'. |
pageToken | string | — | Pagination token from a previous response. |
buOrderTypes | array | — | Bot type filter: futures_grid, spot_grid, smart_copy. Omit to return all types. |
Parameters from the server's own tool schema.
This tool retrieves bot order data from Pionex without side effects. However, severity is elevated to 'medium' rather than 'low' because: (1) the server reads financial trading credentials from ~/.pionex/config.toml, meaning misuse could expose sensitive trading account information; (2) the listed bot orders contain financial trading state that could inform unauthorized trading decisions; (3) the sibling tools…
From the tool's definition Tool name 'list' and description 'List bot orders' indicates retrieval operation. HTTP method is GET /api/v1/bot/orders, which is a query endpoint. No modification, deletion, or execution of external commands occurs.
Attacks that exploit this kind of access
List bot orders with optional filters and pagination. status: 'running' (default) or 'finished'. buOrderTypes: one or more of futures_grid, spot_grid, smart_copy. Endpoint: GET /api/v1/bot/orders. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_bot_order_list accepts 5 parameters: base, quote, status, pageToken, buOrderTypes. 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_order_list: 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_order_list 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_order_list 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_order_list. 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_order_list 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 →