// SCAN REPORT

ClawdPay MCP

3 tools. 2 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

2 can modify or destroy data

1 read-only

3 tools total

Community server · catalogue entry verified 29/06/2026

How to control ClawdPay MCP ↓

TOOL MAP

What ClawdPay MCP exposes to your agents

Read (1) Write / Execute (0) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous ClawdPay MCP tools

Financial · Critical create_virtual_card Creating a virtual card directly enables financial transactions by provisioning a payment instrument linked to real money. Financial · Critical secure_auto_fill This tool performs the act of submitting payment information into checkout forms, directly enabling financial transactions.

2 of ClawdPay MCP's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control ClawdPay MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and ClawdPay MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "create_virtual_card": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "get_funding_sources": {
    "limits": [
      {
        "counter": "get_funding_sources_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register ClawdPay MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CLAWDPAY →

Instant setup, no code required.

FULL CATALOGUE

All 3 ClawdPay MCP tools

FINANCIAL 2 tools

Financial create_virtual_card Create a single-use virtual card via Privacy.com. Returns secure card details. Financial secure_auto_fill Intelligently finds and fills payment fields on the current page using robust heuristics.

READ 1 tools

Read get_funding_sources List available funding accounts connected to Privacy.com

FAQ

Questions about ClawdPay MCP

Can an AI agent move money through the ClawdPay MCP server? +

Yes. The ClawdPay MCP server exposes 2 financial tools including create_virtual_card, secure_auto_fill. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the ClawdPay MCP server expose? +

3 tools across 2 categories: Read, Write. 1 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on ClawdPay MCP? +

Register the ClawdPay MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every ClawdPay MCP tool call.

Deterministic rules across all 3 ClawdPay MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CLAWDPAY →

Instant setup, no code required.

3 ClawdPay MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.