Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (PENDING/FILLING/FILLED/PARTIAL/FAILED/CANCELLED), fill amounts, provider used, on-chain delegatio...
AI agents call get_order to retrieve information from MERX - TRON Resource Exchange without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves order information without modifying, deleting, or executing transactions. While it operates within a financial system (TRON resource exchange), the tool itself only reads data—it polls order progress and returns status details. No financial transactions, deletions, or code execution occur; it is purely informational retrieval.
From the tool's definition Tool name is 'get_order' with aliases 'get_order_status', 'check_order', 'order_status', 'order_details', 'fetch_order'. Description states it 'retrieves...status and fill details of an existing order' and 'Returns current status...fill amounts, provider used.
Attacks that exploit this kind of access
Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (PENDING/FILLING/FILLED/PARTIAL/FAILED/CANCELLED), fill amounts, provider used, on-chain delegation tx hash if delivered. Use this to poll order progress after creating an order. Auth required (API key). It is categorised as a Read tool in the MERX - TRON Resource Exchange MCP Server, which means it retrieves data without modifying state.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for 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 MERX - TRON Resource Exchange. Nothing to install.
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 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 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.
get_order is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-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 →