Get full details of a single standing order by its UUID. Returns trigger config, action params, budget, executions count, and status. Auth required (API key).
AI agents call get_standing_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 is a Read-category tool as it retrieves existing standing order data without creating, modifying, or deleting anything. However, severity is elevated to 'medium' rather than 'low' because: (1) standing orders on a financial exchange can trigger automated transactions, so detailed order configuration data is sensitive; (2) the tool returns 'trigger config' and 'action params' which could reveal how automated…
From the tool's definition Tool performs a retrieval operation: 'Get full details of a single standing order by its UUID. Returns trigger config, action params, budget, executions count, and status.' The verb 'Get' and 'Returns' indicate a read/query action with no modification of data.
Attacks that exploit this kind of access
Get full details of a single standing order by its UUID. Returns trigger config, action params, budget, executions count, and status. 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_standing_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_standing_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_standing_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_standing_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_standing_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 →