# recommend_payment_rail

Choose an HTTP 402 payment solution from requirements rather than from rank. Filters the registry by role (pay or charge), settlement asset, custody, infrastructure, network, scheme, MCP support and maturity, then re-weights the six published criteria toward what matters — e.g. sub-cent amounts weight settlement cost heavily. Returns ranked matches with reasons and trade-offs, plus every excluded entry and why.

Agent View of the PolicyLayer registry record for `recommend_payment_rail`. HTML page: https://policylayer.com/tools/402mcp-mcp/recommend-payment-rail

## Facts

- Tool: `recommend_payment_rail`
- Server: 402mcp (`@402mcp/mcp`) — https://policylayer.com/tools/402mcp-mcp.md
- Install: `npx -y @402mcp/mcp`
- Homepage: https://www.npmjs.com/package/@402mcp/mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 10
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `role` | string | no | pay: an agent paying for resources. charge: a service charging agents. |
| `chain` | string | no | Required network, e.g. lightning, base, solana, tempo. |
| `limit` | integer | no | Maximum recommendations (default 5). |
| `scheme` | string | no | Restrict to one 402 scheme. |
| `custody` | string | no | self: the agent or service must hold its own keys. |
| `needs_mcp` | boolean | no | Require a native MCP server or MCP-native tooling. |
| `infrastructure` | string | no | none: no node or server infrastructure to operate. |
| `production_only` | boolean | no | Exclude alpha, preview, inactive and unstated maturity. |
| `settlement_asset` | string | no | What payments must settle in. |
| `typical_amount_usd` | number | no | Typical payment size in US dollars, e.g. 0.001 for a sub-cent API call. |

Parameters from the server's own tool schema.

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

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

## Why recommend_payment_rail is rated Low

Even though recommend_payment_rail only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (10 properties) · Bulk/mass operation — affects multiple targets

## Use case

AI agents call recommend_payment_rail to retrieve information from 402mcp 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 402mcp:

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

## Other tools on 402mcp (6)

- `decode_402_challenge` — Read — https://policylayer.com/tools/402mcp-mcp/decode-402-challenge.md
- `get_best_payment_solution` — Read — https://policylayer.com/tools/402mcp-mcp/get-best-payment-solution.md
- `get_scheme_reference` — Read — https://policylayer.com/tools/402mcp-mcp/get-scheme-reference.md
- `get_solution` — Read — https://policylayer.com/tools/402mcp-mcp/get-solution.md
- `probe_402_support` — Read — https://policylayer.com/tools/402mcp-mcp/probe-402-support.md
- `search_402_solutions` — Read — https://policylayer.com/tools/402mcp-mcp/search-402-solutions.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=402mcp-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/402mcp-mcp
