// SCAN REPORT

Pop Pay

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

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

Last updated: 30 Jun 2026

2 can modify or destroy data

1 read-only

3 tools total

Community server · catalogue entry checked 30/06/2026

How to control Pop Pay ↓

TOOL MAP

What Pop Pay 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 Pop Pay tools

Financial · Critical request_virtual_card The server context makes clear this is a payment/financial infrastructure server. Financial · Critical request_x402_payment Despite the empty description, the tool name contains 'payment' and it exists on a server whose sole purpose is processing financial transactions for AI agents.

2 of Pop Pay'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 Pop Pay

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

Block financial tools by default

{
  "request_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

{
  "request_purchaser_info": {
    "limits": [
      {
        "counter": "request_purchaser_info_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 Pop Pay — 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 POP PAY →

Instant setup, no code required.

FULL CATALOGUE

All 3 Pop Pay tools

FINANCIAL 2 tools

Financial request_virtual_card request_virtual_card Financial request_x402_payment request_x402_payment

READ 1 tools

Read request_purchaser_info request_purchaser_info

FAQ

Questions about Pop Pay

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

Yes. The Pop Pay server exposes 2 financial tools including request_virtual_card, request_x402_payment. 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 Pop Pay MCP server expose? +

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

How do I enforce a policy on Pop Pay? +

Register the Pop Pay 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 Pop Pay tool call.

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

ENFORCE POLICY ON POP PAY →

Instant setup, no code required.

3 Pop Pay tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Pop Pay's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →