list_pull_payments
AI agents call list_pull_payments 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.
The 'list' prefix strongly suggests data retrieval with no side effects. Pull payments are payment request objects in BTCPay Server that allow recipients to pull funds. Listing them is a read-only query operation. Confidence is moderate (0.72) rather than high because the description is empty, leaving some ambiguity, but the naming pattern is clear.
From the tool's definition Tool name 'list_pull_payments' indicates a retrieval/listing operation. The description is empty, but the naming convention and context (sibling tools include many 'get_' and 'list_' operations) suggest this queries existing pull payment data without…
Attacks that exploit this kind of access
list_pull_payments. 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_pull_payments: 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_pull_payments 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_pull_payments 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_pull_payments. 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_pull_payments 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 →