# request_virtual_card

A financial tool on the Pop Pay MCP server.

Agent View of the PolicyLayer registry record for `request_virtual_card`. HTML page: https://policylayer.com/tools/100xpercent-pop-pay-python/request-virtual-card

## Facts

- Tool: `request_virtual_card`
- Server: Pop Pay (`100xpercent/pop-pay-python`) — https://policylayer.com/tools/100xpercent-pop-pay-python.md
- Homepage: https://github.com/100xPercent/pop-pay-python
- Risk category: Financial (Critical risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Approval-gated

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "request_virtual_card",
    "arguments": {}
  }
}
```

## Why request_virtual_card is rated Critical

The server context makes clear this is a payment/financial infrastructure server. 'request_virtual_card' strongly implies requesting a virtual payment card, which constitutes a financial action — potentially committing financial obligations or enabling future payments.

From the tool's own definition: "Tool name 'request_virtual_card' on a payment-focused server (pop-pay) designed for financial transactions; server description explicitly mentions 'payment guardrail', 'financial transactions', and 'human-controlled credit cards'"

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Approval-gated**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Pop Pay:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_virtual_card": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}
```

## Other tools on Pop Pay (2)

- `request_x402_payment` — Financial — https://policylayer.com/tools/100xpercent-pop-pay-python/request-x402-payment.md
- `request_purchaser_info` — Read — https://policylayer.com/tools/100xpercent-pop-pay-python/request-purchaser-info.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=100xpercent-pop-pay-python · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/100xpercent-pop-pay-python