List on-chain wallet transactions for a payment method.
AI agents call list_wallet_transactions to retrieve information from BTCPay Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical blockchain transaction data for a wallet. It performs a read-only operation that does not create, modify, delete, or execute any actions. The data returned is informational only, suitable for monitoring and reconciliation purposes. No funds are moved, no records are changed, and no code is executed.
From the tool's definition Tool name is 'list_wallet_transactions' and description states 'List on-chain wallet transactions' — the verb 'List' and 'for a payment method' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List on-chain wallet transactions for a payment method. It is categorised as a Read tool in the BTCPay Server MCP MCP Server, which means it retrieves data without modifying state.
Register the BTCPay Server MCP server in PolicyLayer and add a rule for list_wallet_transactions: 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 BTCPay Server MCP. Nothing to install.
list_wallet_transactions 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 list_wallet_transactions 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 list_wallet_transactions. 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.
list_wallet_transactions is provided by the BTCPay Server MCP server (ThomsenDrake/btcpay-mcp). 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 →