Withdraw TRX or USDT from your Merx account to an external TRON address. The
AI agents use withdraw 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 funds (TRX or USDT) from a user's account to an external address. This is a financial operation that commits real monetary value and cannot be easily reversed. It poses critical risk if invoked by an AI agent without proper authorization or safeguards, as it directly results in loss of funds.
From the tool's definition Tool name: withdraw. Description states: 'Withdraw TRX or USDT from your Merx account to an external TRON address.' TRX and USDT are cryptocurrency assets; withdrawal transfers money from a controlled account to an external address.
Attacks that exploit this kind of access
Withdraw TRX or USDT from your Merx account to an external TRON address. The. 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 withdraw: 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.
withdraw 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 withdraw 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 withdraw. 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.
withdraw 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 →