call_contract · MERX - TRON Resource Exchange MCP

WHAT IT DOES

What call_contract does on MERX - TRON Resource Exchange

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

WHY IT NEEDS A POLICY

Why call_contract needs a policy

This tool executes smart contract functions with state-changing effects on TRON blockchain. While not inherently financial (no direct fund movement described), it is Execute-category because it triggers external blockchain operations whose consequences depend on contract logic and arguments provided.

From the tool's definition Tool name 'call_contract' and description 'Execute a state-changing smart contract function' explicitly indicates execution of smart contract operations that modify blockchain state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

call_contract Rate-limited

call_contract stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_contract": {
      "limits": [
        {
          "counter": "call_contract_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MERX - TRON Resource Exchange, so you can run agents against it safely.

FAQ

Questions about call_contract

What does the call_contract tool do? +

Execute a state-changing smart contract function. Estimates resources,. 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? +

Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for call_contract: 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.

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

How do I block call_contract completely? +

Set action: deny in the PolicyLayer 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 (Hovsteder/merx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.