wallet_peerPayments
Lists pending PeerPay payments or receives one selected payment into the embedded BRC-100 wallet. Receiving requires an explicit messageId and internalizes funds before acknowledging the MessageBox item.
This record as markdown: /tools/b-open-io-bsv-mcp/wallet-peerpayments.md
What wallet_peerPayments does on Bitcoin SV MCP Server
AI agents use wallet_peerPayments to commit financial operations through Bitcoin SV MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why wallet_peerPayments is rated Critical
Tool moves cryptocurrency funds into a wallet, constituting a financial operation.
From the tool's definition receives payment, internalizes funds, BRC-100 wallet
Attacks that exploit this kind of access
The rule that runs wallet_peerPayments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin SV MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_peerPayments, this is the rule to start with:
Any call to wallet_peerPayments is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin SV MCP Server, apply this rule, and every wallet_peerPayments call is checked against it from then on.
Questions about wallet_peerPayments
Lists pending PeerPay payments or receives one selected payment into the embedded BRC-100 wallet. Receiving requires an explicit messageId and internalizes funds before acknowledging the MessageBox item. It is categorised as a Financial tool in the Bitcoin SV MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_peerPayments: 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 Bitcoin SV MCP Server. Nothing to install.
wallet_peerPayments is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wallet_peerPayments 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 wallet_peerPayments. 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.
wallet_peerPayments is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bitcoin SV MCP Server, and thousands of servers like it.
Across the catalogue