Deposit TRX to your Merx account. Requires MERX_API_KEY + TRON_PRIVATE_KEY.
AI agents use deposit_trx 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 directly moves cryptocurrency (TRX tokens) from a user's wallet to a Merx exchange account. This is a financial obligation and asset transfer. The critical severity reflects that an AI agent with access to TRON_PRIVATE_KEY could drain wallets or commit substantial financial obligations without user consent.
From the tool's definition Tool named 'deposit_trx' with description 'Deposit TRX to your Merx account.' TRX is the TRON network's native cryptocurrency. Depositing cryptocurrency constitutes a financial transaction that moves money into an account.
Attacks that exploit this kind of access
Deposit TRX to your Merx account. Requires MERX_API_KEY + 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 deposit_trx: 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.
deposit_trx 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 deposit_trx 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 deposit_trx. 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.
deposit_trx 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 →