call_contract

Execute a state-changing smart contract function. Estimates resources, buys via Merx if needed. Requires TRON_PRIVATE_KEY and TRON_ADDRESS.

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

merx-mcp Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke call_contract 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.

// WHY ENFORCE A POLICY ON CALL_CONTRACT

call_contract 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.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

merx-tron-resource-exchange.yaml

tools:
  call_contract:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

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

// DETAILS

Tool Name call_contract

Category Execute

MCP Server MERX - TRON Resource Exchange MCP Server

Risk Level High

// MORE MERX - TRON RESOURCE EXCHANGE TOOLS

Financial deposit_trx Financial enable_auto_deposit Financial pay_invoice Financial transfer_trc20 Financial transfer_trx Financial withdraw Execute compile_policy Execute execute_intent

View all 54 tools →

// RELATED READING

// FAQ

What does the call_contract tool do? +

Execute a state-changing smart contract function. Estimates resources, buys via Merx if needed. Requires TRON_PRIVATE_KEY and TRON_ADDRESS.. 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.

How do I enforce a policy on call_contract? +

Add a rule in your Intercept YAML policy under the tools section for call_contract. 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 call_contract? +

call_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_contract? +

Yes. Add a rate_limit block to the call_contract 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 call_contract completely? +

Set action: deny in the Intercept policy for call_contract. 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 call_contract? +

call_contract 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.

call_contract

Enforce policies on MERX - TRON Resource Exchange