create_pull_payment · BTCPay Server MCP: Risk & Policy

WHAT IT DOES

What create_pull_payment does on BTCPay Server MCP

AI agents use create_pull_payment to create or update resources in BTCPay Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BTCPay Server MCP environment.

WHY IT NEEDS A POLICY

Why create_pull_payment needs a policy

A pull payment is a reversible financial authorization mechanism (creating a pull payment request does not immediately move funds). This is Write rather than Execute or Financial because the tool creates a configuration/record for future payment authorization, not an immediate financial transaction. However, severity is high because misuse could authorize unauthorized payments against merchant accounts.

From the tool's definition Tool name 'create_pull_payment' indicates creation of a financial pull payment request in BTCPay Server. The tool name matches the semantic pattern of sibling tools like 'create_invoice' and 'create_payment_request'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_pull_payment Rate-limited

create_pull_payment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_pull_payment": {
      "limits": [
        {
          "counter": "create_pull_payment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BTCPay Server MCP, so you can run agents against it safely.

FAQ

Questions about create_pull_payment

What does the create_pull_payment tool do? +

create_pull_payment. It is categorised as a Write tool in the BTCPay Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_pull_payment? +

Register the BTCPay Server MCP server in PolicyLayer and add a rule for create_pull_payment: 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.

What risk level is create_pull_payment? +

create_pull_payment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_pull_payment? +

Yes. Add a rate_limit block to the create_pull_payment 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 create_pull_payment completely? +

Set action: deny in the PolicyLayer policy for create_pull_payment. 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 create_pull_payment? +

create_pull_payment 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.