Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY.
AI agents use execute_swap to commit financial operations through MERX - TRON Resource Exchange — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs a financial transaction — swapping tokens on a decentralized exchange (SunSwap V2). Token swaps move assets/funds and commit financial obligations. Use of a private key confirms real on-chain transactions. Misuse by an AI agent could result in irreversible loss of funds, making this critical severity.
From the tool's definition Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY.
Attacks that exploit this kind of access
Execute a token swap on SunSwap V2. Requires TRON_PRIVATE_KEY. It is categorised as a Financial tool in the MERX - TRON Resource Exchange MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for execute_swap: 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.
execute_swap is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the execute_swap 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.
Set action: deny in the PolicyLayer 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.
execute_swap 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →