x402_payment_request

A financial tool on the X402 Middleware MCP server.

SERVERX402 Middleware SOURCE@gadgethumans/x402

Critical RISK CLASS

Category Financial

Parameters 20 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-payment-request.md

WHAT IT DOES

What x402_payment_request does on X402 Middleware

AI agents use x402_payment_request 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
`amount`	number	—
`description`	string	—

Parameters from the server's own tool schema.

RISK

Why x402_payment_request is rated Critical

The x402 protocol is an HTTP payment protocol, and the server is explicitly described as payment middleware using Stripe. A tool named 'payment_request' on such a server almost certainly initiates or commits financial transactions. Despite the empty description, the naming context is highly indicative of financial operations.

From the tool's definition Tool name 'x402_payment_request' combined with server description 'x402 + Stripe payment middleware' and 'The Stripe for the agent economy' strongly implies this tool initiates or processes financial payment requests.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

x402_payment_request Approval-gated

Any call to x402_payment_request 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_payment_request": {
      "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_payment_request call is checked against it from then on.

FAQ

Questions about x402_payment_request

What does the x402_payment_request tool do? +

x402_payment_request 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_payment_request accept? +

x402_payment_request accepts 2 parameters: amount, description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on x402_payment_request? +

Register the X402 Middleware MCP server in PolicyLayer and add a rule for x402_payment_request: 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_payment_request? +

x402_payment_request 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_payment_request? +

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

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

x402_payment_request 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 →uber_request_ride on MCP Uber Server →pay_x402 on 8004swap →x402_call on X402 Buyer → All critical-risk MCP tools → The MCP Attack Database →

Guides

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