MERX - TRON Resource Exchange

66 tools. 28 can modify or destroy data without limits.

8 destructive tools with no built-in limits. Policy required.

Last updated:

28 can modify or destroy data
38 read-only
66 tools total
Read (38) Write / Execute (20) Destructive / Financial (8)

Financial operations (deposit_trx, enable_auto_deposit, pay_invoice) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Destructive tools (cancel_monitor, cancel_standing_order) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (approve_trc20, convert_address, create_account) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (call_contract, compile_policy, execute_intent) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Block financial tools by default
deposit_trx:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
cancel_monitor:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
approve_trc20:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
agent_status:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent move money through the MERX - TRON Resource Exchange MCP server? +

Yes. The MERX - TRON Resource Exchange server exposes 6 financial tools including deposit_trx, enable_auto_deposit, pay_invoice. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the MERX - TRON Resource Exchange MCP server? +

Yes. The MERX - TRON Resource Exchange server exposes 2 destructive tools including cancel_monitor, cancel_standing_order. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MERX - TRON Resource Exchange? +

The MERX - TRON Resource Exchange server has 14 write tools including approve_trc20, convert_address, create_account. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the MERX - TRON Resource Exchange MCP server expose? +

66 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 38 are read-only. 28 can modify, create, or delete data.

How do I add Intercept to my MERX - TRON Resource Exchange setup? +

One line change. Instead of running the MERX - TRON Resource Exchange server directly, prefix it with Intercept: intercept -c merx-tron-resource-exchange.yaml -- npx -y @merx-mcp. Download a pre-built policy from policylayer.com/policies/merx-tron-resource-exchange and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.