Block until an order reaches a terminal state (FILLED, PARTIAL, FAILED, or CANCELLED) by polling get_order at fixed intervals. Use this right after create_order when you need to confirm the energy/bandwidth has actually been delegated on-chain before sending the next transaction. Returns the fina...
AI agents invoke wait_for_delegation to trigger actions in MERX - TRON Resource Exchange. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a blocking operation that waits for on-chain delegation completion and returns transaction hashes. While not destructive or financial on its own, it is an Execute category tool because it: (1) triggers/monitors external blockchain operations, (2) requires authentication, and (3) its effects depend on prior delegated resource amounts, making misuse capable of committing unintended delegations.
From the tool's definition Tool description explicitly states it 'Block until an order reaches a terminal state' and 'confirm the energy/bandwidth has actually been delegated on-chain before sending the next transaction', indicating it monitors and may trigger transaction execution on…
Attacks that exploit this kind of access
Block until an order reaches a terminal state (FILLED, PARTIAL, FAILED, or CANCELLED) by polling get_order at fixed intervals. Use this right after create_order when you need to confirm the energy/bandwidth has actually been delegated on-chain before sending the next transaction. Returns the final order details including the on-chain delegation tx hash. Auth required. It is categorised as a Execute tool in the MERX - TRON Resource Exchange MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for wait_for_delegation: 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.
wait_for_delegation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_delegation 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 wait_for_delegation. 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.
wait_for_delegation 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 →