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...
Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke wait_for_delegation to trigger processes or run actions in MERX - TRON Resource Exchange. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
wait_for_delegation can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
wait_for_delegation:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full MERX - TRON Resource Exchange policy for all 66 tools.
Agents calling execute-class tools like wait_for_delegation have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
wait_for_delegation is one of the high-risk operations in MERX - TRON Resource Exchange. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
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.
Add a rule in your Intercept YAML policy under the tools section for wait_for_delegation. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MERX - TRON Resource Exchange MCP server.
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 Intercept 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 Intercept 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 (merx-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.