x402_purchase_credits

Create or top up reusable developer credits through x402.

SERVERWisely x402 Agent-Payment Infrastructure SOURCEhttps://payments.wiselyenterprisesllc.com/ai/mcp

Critical RISK CLASS

Category Financial

Parameters 120 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wiselyenterprisesllc-x402-agent-payment-infrastructure/x402-purchase-credits.md

WHAT IT DOES

What x402_purchase_credits does on Wisely x402 Agent-Payment Infrastructure

AI agents use x402_purchase_credits to commit financial operations through Wisely x402 Agent-Payment Infrastructure, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`url`	string	—
`type`	string	—
`asset`	string	—
`input`	object	—	Public-safe request body/input for a hosted service or endpoint. Never include secrets, raw cards, wallet keys, passwords, or private account tokens.
`items`	array	—
`query`	string	—
`since`	string	—
`itemId`	string	—
`accepts`	array	—
`content`	string	—	Public-safe creator content for preview/import. Do not include secrets, private student data, or copyrighted material you do not own.
`network`	string	—
`audience`	string	—	Optional audience hint for wisely_start_here / wisely_get_playbook / wisely_agent_instructions.

Parameters from the server's own tool schema.

RISK

Why x402_purchase_credits is rated Critical

Purchasing or topping up credits is a financial transaction that directly moves funds or commits payment obligations. The server is explicitly described as payment infrastructure ('x402/MCP payments'), and the tool name 'x402_purchase_credits' combined with the description confirms a financial transaction. Misuse by an AI agent could result in unauthorized spending of real funds, warranting critical severity.

From the tool's definition 'Create or top up reusable developer credits through x402' — this tool moves money/commits financial obligations by purchasing credits via the x402 payment protocol.

Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (content) · High parameter count (43 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x402_purchase_credits safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wisely x402 Agent-Payment Infrastructure, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x402_purchase_credits, this is the rule to start with:

x402_purchase_credits Approval-gated

Any call to x402_purchase_credits 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_purchase_credits": {
      "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 Wisely x402 Agent-Payment Infrastructure, apply this rule, and every x402_purchase_credits call is checked against it from then on.

FAQ

Questions about x402_purchase_credits

What does the x402_purchase_credits tool do? +

Create or top up reusable developer credits through x402. It is categorised as a Financial tool in the Wisely x402 Agent-Payment Infrastructure MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does x402_purchase_credits accept? +

x402_purchase_credits accepts 12 parameters: url, type, asset, input, items, query, since, itemId, accepts, content, network, audience. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on x402_purchase_credits? +

Register the Wisely x402 Agent-Payment Infrastructure MCP server in PolicyLayer and add a rule for x402_purchase_credits: 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 Wisely x402 Agent-Payment Infrastructure. Nothing to install.

What risk level is x402_purchase_credits? +

x402_purchase_credits 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_purchase_credits? +

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

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

x402_purchase_credits is provided by the Wisely x402 Agent-Payment Infrastructure MCP server (https://payments.wiselyenterprisesllc.com/ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wisely x402 Agent-Payment Infrastructure, and thousands of servers like it.

This server

All 65 Wisely x402 Agent-Payment Infrastructure tools → Critical-risk tools on this server →

Across the catalogue

request_x402_payment on Pop Pay →x402_call on X402 Buyer →purchase_external_order on Thinkific MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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