Medium Risk

convert_address

Convert TRON address between base58 (T...) and hex (41...) formats. 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 Write Risk 2/5

AI agents use convert_address 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 convert_address 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.

merx-tron-resource-exchange.yaml
tools:
  convert_address:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

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

Tool Name convert_address
Category Write
Risk Level Medium

View all 54 tools →

What does the convert_address tool do? +

Convert TRON address between base58 (T...) and hex (41...) formats. 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.

How do I enforce a policy on convert_address? +

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

convert_address is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit convert_address? +

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

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

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