Low Risk

estimate_transaction_cost

Estimate energy and bandwidth cost for a TRON transaction. Compares rental vs burn cost. No auth required.

Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

merx-mcp Read

AI agents call estimate_transaction_cost to retrieve information from MERX - TRON Resource Exchange without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though estimate_transaction_cost only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

merx-tron-resource-exchange.yaml
tools:
  estimate_transaction_cost:
    rules:
      - action: allow

See the full MERX - TRON Resource Exchange policy for all 54 tools.

Tool Name estimate_transaction_cost
Category Read
Risk Level Low

View all 54 tools →

What does the estimate_transaction_cost tool do? +

Estimate energy and bandwidth cost for a TRON transaction. Compares rental vs burn cost. No 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.

How do I enforce a policy on estimate_transaction_cost? +

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.

What risk level is estimate_transaction_cost? +

estimate_transaction_cost is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estimate_transaction_cost? +

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.

How do I block estimate_transaction_cost completely? +

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.

What MCP server provides estimate_transaction_cost? +

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.

Enforce policies on MERX - TRON Resource Exchange

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.