Estimate cost of a TRON transaction BEFORE sending. Aliases: estimate_cost, calculate_cost, transaction_cost, energy_cost, transfer_cost. Calculate exactly how much energy, bandwidth, and TRX a TRON transaction will cost before sending it. Use this to answer questions like "how much does a USDT t...
Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use estimate_transaction_cost to create or modify resources in MERX - TRON Resource Exchange. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call estimate_transaction_cost repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MERX - TRON Resource Exchange.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
estimate_transaction_cost:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full MERX - TRON Resource Exchange policy for all 66 tools.
Agents calling write-class tools like estimate_transaction_cost have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Estimate cost of a TRON transaction BEFORE sending. Aliases: estimate_cost, calculate_cost, transaction_cost, energy_cost, transfer_cost. Calculate exactly how much energy, bandwidth, and TRX a TRON transaction will cost before sending it. Use this to answer questions like "how much does a USDT transfer cost?" or "what will it cost me to send 100 USDT to address X?". Returns: energy units needed, bandwidth needed, TRX cost if you burn directly, and TRX cost if you rent energy from Merx (typically 70-80% cheaper). Supports trc20_transfer (e.g. USDT/USDC), trc20_approve, trx_transfer, and custom contract calls. No auth required.. It is categorised as a Write tool in the MERX - TRON Resource Exchange MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for estimate_transaction_cost. 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.
estimate_transaction_cost is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the estimate_transaction_cost 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 estimate_transaction_cost. 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.
estimate_transaction_cost 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.