util_base_usdc_payment_match

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

Low RISK CLASS

Category Read

Parameters 55 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-base-usdc-payment-match.md

WHAT IT DOES

What util_base_usdc_payment_match does on Delx Protocol — Agent Recovery & Continuity

AI agents call util_base_usdc_payment_match to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`chain_id`	integer	Yes	Chain Id supplied to Base USDC Payment Match; used only for this bounded calculation and processed in memory without retention.
`recipient`	string	Yes	Recipient supplied to Base USDC Payment Match; used only for this bounded calculation and processed in memory without retention.
`amount_raw`	string	Yes	Amount Raw supplied to Base USDC Payment Match; used only for this bounded calculation and processed in memory without retention.
`expected_recipient`	string	Yes	Expected Recipient supplied to Base USDC Payment Match; used only for this bounded calculation and processed in memory without retention.
`expected_amount_raw`	string	Yes	Expected Amount Raw supplied to Base USDC Payment Match; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

RISK

Why util_base_usdc_payment_match is rated Low

Even though util_base_usdc_payment_match only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_base_usdc_payment_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_base_usdc_payment_match, this is the rule to start with:

util_base_usdc_payment_match Allowed

util_base_usdc_payment_match is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "util_base_usdc_payment_match": {}
  }
}

ALLOW ONLY 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_base_usdc_payment_match call is checked against it from then on.

FAQ

Questions about util_base_usdc_payment_match

What does the util_base_usdc_payment_match tool do? +

Base USDC Payment Match checks recipient, raw amount, and chain id for a Base USDC payment intent from bounded caller-supplied values without an external provider. Call Base USDC Payment Match before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for Base USDC Payment Match as versioned deterministic JSON. Limitation: Uses caller-supplied values only; it performs no RPC call, signing, broadcasting, balance lookup, custody, trading, or live-chain claim. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.

What parameters does util_base_usdc_payment_match accept? +

util_base_usdc_payment_match accepts 5 parameters: chain_id, recipient, amount_raw, expected_recipient, expected_amount_raw. Required: chain_id, recipient, amount_raw, expected_recipient, expected_amount_raw. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_base_usdc_payment_match? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_base_usdc_payment_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_base_usdc_payment_match? +

util_base_usdc_payment_match is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit util_base_usdc_payment_match? +

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

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

util_base_usdc_payment_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 →

Across the catalogue

match_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →