New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERBitcoin SV MCP Server SOURCEb-open-io/bsv-mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about wallet_peerPayments

What does the wallet_peerPayments tool do? +

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.

How do I enforce a policy on wallet_peerPayments? +

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.

What risk level is wallet_peerPayments? +

wallet_peerPayments is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit wallet_peerPayments? +

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.

How do I block wallet_peerPayments completely? +

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.

What MCP server provides wallet_peerPayments? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bitcoin SV MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.