New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

util_x402_lifecycle_reconcile

Reconcile one x402 purchase end to end: submit bounded, non-secret metadata for the payment requirement, payment response, delivery receipt and settlement reference, and receive a single deterministic verdict — proven, conflicting, or missing — field by field, suitable to attach to a refund reque...

SERVERDelx Mcp A2a SOURCEhttps://api.delx.ai/v1/mcp
Low RISK CLASS
Category Read
Parameters 44 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-x402-lifecycle-reconcile.md

What util_x402_lifecycle_reconcile does on Delx Mcp A2a

AI agents call util_x402_lifecycle_reconcile to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
settlement_ref object Yes Bounded settlement reference metadata. No private keys.
delivery_receipt object Yes Bounded delivery receipt metadata. No payload bodies or secrets.
payment_response object Yes Bounded non-secret payment response metadata. No signatures.
payment_requirement object Yes Bounded non-secret payment requirement metadata from the 402.

Parameters from the server's own tool schema.

Why util_x402_lifecycle_reconcile is rated Low

Even though util_x402_lifecycle_reconcile 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.

Questions about util_x402_lifecycle_reconcile

What does the util_x402_lifecycle_reconcile tool do? +

Reconcile one x402 purchase end to end: submit bounded, non-secret metadata for the payment requirement, payment response, delivery receipt and settlement reference, and receive a single deterministic verdict — proven, conflicting, or missing — field by field, suitable to attach to a refund request. Limitation: verdicts are computed from the artifacts you provide; we do not fetch chain state or contact the provider on your behalf. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.

What parameters does util_x402_lifecycle_reconcile accept? +

util_x402_lifecycle_reconcile accepts 4 parameters: settlement_ref, delivery_receipt, payment_response, payment_requirement. Required: settlement_ref, delivery_receipt, payment_response, payment_requirement. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_x402_lifecycle_reconcile? +

Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_x402_lifecycle_reconcile: 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 Mcp A2a. Nothing to install.

What risk level is util_x402_lifecycle_reconcile? +

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

Can I rate-limit util_x402_lifecycle_reconcile? +

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

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

util_x402_lifecycle_reconcile is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Delx Mcp A2a, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx Mcp A2a's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.