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 w...
This record as markdown: /tools/402mcp-mcp/recommend-payment-rail.md
What recommend_payment_rail does on 402mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | — | pay: an agent paying for resources. charge: a service charging agents. |
chain | string | — | Required network, e.g. lightning, base, solana, tempo. |
limit | integer | — | Maximum recommendations (default 5). |
scheme | string | — | Restrict to one 402 scheme. |
custody | string | — | self: the agent or service must hold its own keys. |
needs_mcp | boolean | — | Require a native MCP server or MCP-native tooling. |
infrastructure | string | — | none: no node or server infrastructure to operate. |
production_only | boolean | — | Exclude alpha, preview, inactive and unstated maturity. |
settlement_asset | string | — | What payments must settle in. |
typical_amount_usd | number | — | Typical payment size in US dollars, e.g. 0.001 for a sub-cent API call. |
Parameters from the server's own tool schema.
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 signalsHigh parameter count (10 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs recommend_payment_rail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recommend_payment_rail, this is the rule to start with:
recommend_payment_rail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 402mcp, apply this rule, and every recommend_payment_rail call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the 402mcp MCP Server, which means it retrieves data without modifying state.
recommend_payment_rail accepts 10 parameters: role, chain, limit, scheme, custody, needs_mcp, infrastructure, production_only, settlement_asset, typical_amount_usd. The full parameter table on this page comes from the server's own tool schema.
Register the 402 MCP server in PolicyLayer and add a rule for recommend_payment_rail: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 402mcp. Nothing to install.
recommend_payment_rail is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the recommend_payment_rail rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for recommend_payment_rail. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
recommend_payment_rail is provided by the 402 MCP server (@402mcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402, and thousands of servers like it.
This server
Across the catalogue