x402_verify_payment

A financial tool on the X402 Middleware MCP server.

SERVERX402 Middleware SOURCE@gadgethumans/x402

Critical RISK CLASS

Category Financial

Parameters 11 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/x402-verify-payment.md

WHAT IT DOES

What x402_verify_payment does on X402 Middleware

AI agents use x402_verify_payment to commit financial operations through X402 Middleware, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`payment_header`	string	Yes

Parameters from the server's own tool schema.

RISK

Why x402_verify_payment is rated Critical

The tool name explicitly references payment verification within a payment middleware server built on Stripe. Verifying a payment is a financial operation — it confirms or validates a financial transaction. While the description is empty (reducing confidence), the server context strongly implies this tool interacts with financial transaction state. Under the most-severe-applicable rule, Financial applies.

From the tool's definition Tool name 'x402_verify_payment' combined with server description 'x402 + Stripe payment middleware' and 'The Stripe for the agent economy'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x402_verify_payment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x402_verify_payment, this is the rule to start with:

x402_verify_payment Approval-gated

Any call to x402_verify_payment 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": {
    "x402_verify_payment": {
      "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 X402 Middleware, apply this rule, and every x402_verify_payment call is checked against it from then on.

FAQ

Questions about x402_verify_payment

What does the x402_verify_payment tool do? +

x402_verify_payment is a financial tool on the X402 Middleware MCP server. It is categorised as a Financial tool in the X402 Middleware MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does x402_verify_payment accept? +

x402_verify_payment accepts 1 parameter: payment_header. Required: payment_header. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on x402_verify_payment? +

Register the X402 Middleware MCP server in PolicyLayer and add a rule for x402_verify_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 X402 Middleware. Nothing to install.

What risk level is x402_verify_payment? +

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

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

How do I block x402_verify_payment completely? +

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

What MCP server provides x402_verify_payment? +

x402_verify_payment is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on X402 Middleware, and thousands of servers like it.

This server

All 58 X402 Middleware tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →pay_x402 on 8004swap →x402_call on X402 Buyer →create_payment on Shopmonkey MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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