Get a single order by client order ID.
AI agents call pionex_orders_get_order_by_client_order_id 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 |
|---|---|---|---|
symbol | string | Yes | e.g. BTC_USDT |
clientOrderId | string | Yes | Client order id |
Parameters from the server's own tool schema.
This tool queries and retrieves order data by ID. It performs a read-only lookup operation with no side effects, data modification, or financial transactions. The low severity reflects minimal risk from misuse - an agent could only access existing order information it likely already has context for.
From the tool's definition Tool name contains 'get' and description states 'Get a single order by client order ID' - retrieves order information without modification.
Attacks that exploit this kind of access
Get a single order by client order ID. It is categorised as a Read tool in the Pionex Trade MCP Server, which means it retrieves data without modifying state.
pionex_orders_get_order_by_client_order_id accepts 2 parameters: symbol, clientOrderId. Required: symbol, clientOrderId. 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_order_by_client_order_id: 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_order_by_client_order_id 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_order_by_client_order_id 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_order_by_client_order_id. 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_order_by_client_order_id 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 →