Critical Risk

pay_invoice

Pay an x402 invoice by sending TRX and verifying payment.

Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

merx-mcp Financial Risk 5/5

AI agents use pay_invoice to initiate financial transactions through MERX - TRON Resource Exchange. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

pay_invoice moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

merx-tron-resource-exchange.yaml
tools:
  pay_invoice:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full MERX - TRON Resource Exchange policy for all 54 tools.

Tool Name pay_invoice
Category Financial
Risk Level Critical

View all 54 tools →

What does the pay_invoice tool do? +

Pay an x402 invoice by sending TRX and verifying payment.. 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.

How do I enforce a policy on pay_invoice? +

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

pay_invoice is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pay_invoice? +

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

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

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