wallet_pay

Sends a native ETH or ERC-20 Base payment, subject to execution enablement, recipient blacklist, and optional per-asset amount caps.

SERVERAwesome Base SOURCEB5-Software/awesome-base-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/awesome-base-mcp/wallet-pay.md

WHAT IT DOES

What wallet_pay does on Awesome Base

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

RISK

Why wallet_pay is rated Critical

Directly moves cryptocurrency funds, creating irreversible financial obligations and transfers.

From the tool's definition Sends native ETH or ERC-20 Base payment

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wallet_pay safely

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

wallet_pay Approval-gated

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

FAQ

Questions about wallet_pay

What does the wallet_pay tool do? +

Sends a native ETH or ERC-20 Base payment, subject to execution enablement, recipient blacklist, and optional per-asset amount caps. It is categorised as a Financial tool in the Awesome Base MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on wallet_pay? +

Register the Awesome Base MCP server in PolicyLayer and add a rule for wallet_pay: 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 Awesome Base. Nothing to install.

What risk level is wallet_pay? +

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

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

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

wallet_pay is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Awesome Base, and thousands of servers like it.

This server

All 44 Awesome Base tools → Critical-risk tools on this server →

Across the catalogue

pay_domain on 262 →pay_x402 on 8004swap →export_wallet on Conviction →pay_invoice on Bitcoin MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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