AI agents call pionex.orders.get_order_by_client_order_id to retrieve information from Pionex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_order_by_client_order_id' strongly suggests a read/query operation that retrieves a specific order using a client-provided order ID. This is consistent with the sibling tools pattern (get_order, get_open_orders, get_all_orders are all Read operations). However, confidence is reduced because the description is empty and no explicit description confirms the behavior.
From the tool's definition Tool name contains 'get_order' which implies retrieval; sibling tools follow REST patterns where 'get_' prefix indicates read operations
Attacks that exploit this kind of access
pionex.orders.get_order_by_client_order_id. It is categorised as a Read tool in the Pionex MCP Server, which means it retrieves data without modifying state.
Register the Pionex 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. 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 MCP server (pionex-mcp-server). 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 →