High Risk

execute_swap

Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY.

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

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

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

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

merx-tron-resource-exchange.yaml
tools:
  execute_swap:
    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.

Tool Name execute_swap
Category Execute
Risk Level High

View all 54 tools →

What does the execute_swap tool do? +

Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY.. 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 execute_swap? +

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

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

Can I rate-limit execute_swap? +

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

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

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