List recent orders with optional status filter. Auth required.
AI agents call list_orders 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 retrieves and displays order information without creating, modifying, or deleting data. It performs a simple listing/query operation typical of Read category tools. The authentication requirement protects against unauthorized access but does not change the fundamental read-only nature of the operation. No side effects or state changes result from its use.
From the tool's definition Tool name 'list_orders' and description 'List recent orders' indicate a query/retrieval operation. The phrase 'with optional status filter' and 'Auth required' confirm this is a read-only lookup of existing data with no modification capability.
Attacks that exploit this kind of access
List recent orders with optional status filter. Auth required. 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 list_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 MERX - TRON Resource Exchange. Nothing to install.
list_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 list_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 list_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.
list_orders 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 →