List local bank-rail / wallet payment methods relevant to HelloBooks invoice collection (AR), B2B supplier payments (AP), and contractor payouts (UPI, RuPay, Razorpay, IMPS, NEFT, RTGS, BACS, FPS, CHAPS, Open Banking, Interac e-Transfer, EFT, PayID, PayTo, NPP, BPAY, ACH, Same Day ACH, Fedwire, R...
AI agents call local_payment_methods to retrieve information from HelloBooks AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Return a single payment method by id (e.g. "in-upi", "au-payid", "us-rtp"). |
rail | string | — | Filter by settlement rail (instant, same-day, next-day, multi-day). |
country | string | — | Filter to one country (IN, US, CA, GB, AU, AE, SG, NZ). |
useCase | string | — | Filter by payment use-case. Defaults to HelloBooks' invoice-collection + b2b-supplier + contractor-payout scope; pass an explicit value to widen. |
Parameters from the server's own tool schema.
This tool retrieves and filters information about payment methods available in HelloBooks—rail types, use-cases, caps, settlement windows—but does not itself execute payments, move money, or commit financial obligations. It is informational/reference data for AR/AP/payout workflows, not the mechanism that processes those payments.
From the tool's definition Tool name 'local_payment_methods' and description 'List local bank-rail / wallet payment methods' with action verbs 'returns' and 'filter by' indicate data retrieval only.
Attacks that exploit this kind of access
List local bank-rail / wallet payment methods relevant to HelloBooks invoice collection (AR), B2B supplier payments (AP), and contractor payouts (UPI, RuPay, Razorpay, IMPS, NEFT, RTGS, BACS, FPS, CHAPS, Open Banking, Interac e-Transfer, EFT, PayID, PayTo, NPP, BPAY, ACH, Same Day ACH, Fedwire, RTP, Zelle, PayNow, FAST, GIRO, NZ Direct Credit, etc.). Returns rail (instant / same-day / next-day / multi-day), use-cases, issuing authority, HelloBooks support level, and operational notes (per-transaction caps, settlement windows, retirement timelines). Filter by country, useCase, rail, or id. It is categorised as a Read tool in the HelloBooks AI MCP Server MCP Server, which means it retrieves data without modifying state.
local_payment_methods accepts 4 parameters: id, rail, country, useCase. The full parameter table on this page comes from the server's own tool schema.
Register the HelloBooks AI MCP Server MCP server in PolicyLayer and add a rule for local_payment_methods: 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 HelloBooks AI MCP Server. Nothing to install.
local_payment_methods 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 local_payment_methods 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 local_payment_methods. 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.
local_payment_methods is provided by the HelloBooks AI MCP Server MCP server (Meru-Fin-Tech/HelloBooks-MCP-Public). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →