util_x402_pay_to_match

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry

Critical RISK CLASS

Category Financial

Parameters 22 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-x402-pay-to-match.md

WHAT IT DOES

What util_x402_pay_to_match does on Delx Protocol — Agent Recovery & Continuity

AI agents use util_x402_pay_to_match to commit financial operations through Delx Protocol — Agent Recovery & Continuity, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`pay_to`	string	Yes	Pay To supplied to X402 Pay To Match; used only for this bounded calculation and processed in memory without retention.
`expected`	string	Yes	Expected supplied to X402 Pay To Match; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

RISK

Why util_x402_pay_to_match is rated Critical

util_x402_pay_to_match moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_x402_pay_to_match safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_x402_pay_to_match, this is the rule to start with:

util_x402_pay_to_match Approval-gated

Any call to util_x402_pay_to_match is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "util_x402_pay_to_match": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_x402_pay_to_match call is checked against it from then on.

FAQ

Questions about util_x402_pay_to_match

What does the util_x402_pay_to_match tool do? +

X402 Pay To Match compares challenge pay-to address with an expected merchant address from bounded caller-supplied values without an external provider. Call X402 Pay To Match before paying for or accepting an x402 or agent delivery assembled from caller-supplied challenge and result metadata. Returns contract-specific checks, normalized evidence, mismatch reasons, and an explicit acceptance or rejection status for X402 Pay To Match as versioned deterministic JSON. Limitation: Validates metadata only; it never settles payment, signs payloads, contacts a facilitator, refunds funds, or asserts on-chain truth. It is categorised as a Financial tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does util_x402_pay_to_match accept? +

util_x402_pay_to_match accepts 2 parameters: pay_to, expected. Required: pay_to, expected. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_x402_pay_to_match? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_x402_pay_to_match: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.

What risk level is util_x402_pay_to_match? +

util_x402_pay_to_match 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 util_x402_pay_to_match? +

Yes. Add a rate_limit block to the util_x402_pay_to_match 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.

How do I block util_x402_pay_to_match completely? +

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

util_x402_pay_to_match is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.

This server

All 1076 Delx Protocol — Agent Recovery & Continuity tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →x402_call on X402 Buyer →pay_invoice on Bitcoin MCP Server →invoice_issued_match_payment on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →