List all payment requests (reusable payment links) for the store.
AI agents call list_payment_requests 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 payment request data from the store but does not create, modify, delete, or trigger any operations. It is purely informational in nature. The severity is low because reading metadata about payment requests poses minimal risk; the data returned is non-sensitive transaction metadata that merchants would typically have authorized access to review.
From the tool's definition Tool name is 'list_payment_requests' and description states it 'List all payment requests'. The verb 'list' is a read-only operation that retrieves and queries data without modification or side effects.
Attacks that exploit this kind of access
List all payment requests (reusable payment links) for the store. 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_payment_requests: 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_payment_requests 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_payment_requests 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_payment_requests. 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_payment_requests 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 →