Create a TRC20 payment request on TRON (USDT, USDC, USDD, or any TRC20). Returns a payment address. Fires webhook when payment arrives (<3 seconds). Use for receiving payments from other agents or humans. Requires agent registration first — call register_agent if you get AGENT_NOT_REGISTERED error.
AI agents use request_payment 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 initiates financial transactions on the TRON blockchain, specifically creating payment requests for cryptocurrency transfers (USDT, USDC, USDD). It directly involves moving monetary value, qualifying it as Financial. Severity is critical because misuse could result in unauthorized fund collection, misdirected payments, or financial fraud involving real cryptocurrency assets.
From the tool's definition 'Create a TRC20 payment request on TRON (USDT, USDC, USDD, or any TRC20)' and 'Use for receiving payments from other agents or humans'
Attacks that exploit this kind of access
Create a TRC20 payment request on TRON (USDT, USDC, USDD, or any TRC20). Returns a payment address. Fires webhook when payment arrives (<3 seconds). Use for receiving payments from other agents or humans. Requires agent registration first — call register_agent if you get AGENT_NOT_REGISTERED error. 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 request_payment: 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.
request_payment 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 request_payment 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 request_payment. 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.
request_payment 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 →