List order history for a symbol (filled and cancelled), with optional limit.
AI agents call pionex_orders_get_all_orders 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 |
|---|---|---|---|
limit | integer | — | Default 1 (1-100) |
symbol | string | Yes | e.g. BTC_USDT |
Parameters from the server's own tool schema.
This tool retrieves and queries past order data (filled and cancelled orders) without modifying, executing external operations, or having destructive side effects. The 'limit' parameter is a read-only query filter.
From the tool's definition Tool name includes 'get' and description states 'List order history' with no mention of creation, modification, or deletion of orders. Returns historical data only.
Attacks that exploit this kind of access
List order history for a symbol (filled and cancelled), with optional limit. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_orders_get_all_orders accepts 2 parameters: limit, symbol. Required: symbol. 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_orders_get_all_orders: 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_orders_get_all_orders 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_orders_get_all_orders 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_orders_get_all_orders. 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_orders_get_all_orders 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 →