# request_purchaser_info

A read tool on the Pop Pay MCP server.

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

## Facts

- Tool: `request_purchaser_info`
- 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: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why request_purchaser_info is rated Low

The tool appears to retrieve purchaser information without modifying or executing transactions. However, confidence is moderate due to lack of descriptive detail. In a payment guardrail system, retrieving purchaser details is a necessary precondition for financial operations but does not itself move money or trigger irreversible actions, classifying it as Read rather than Financial/Destructive/Execute.

From the tool's own definition: "Tool name 'request_purchaser_info' indicates retrieval of purchaser information. Description is empty, limiting evidence, but the naming convention follows a query/retrieval pattern (request_*) consistent with Read operations."

## Use case

AI agents call request_purchaser_info to retrieve information from Pop Pay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_purchaser_info": {}
  }
}
```

## Other tools on Pop Pay (2)

- `request_virtual_card` — Financial — https://policylayer.com/tools/100xpercent-pop-pay-python/request-virtual-card.md
- `request_x402_payment` — Financial — https://policylayer.com/tools/100xpercent-pop-pay-python/request-x402-payment.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