Critical Risk →

create_payment

Create a Lightning invoice to pay for one AI service call. Returns JSON: { paymentId, invoice (BOLT11), amount (sats), expiresAt }. Each payment covers exactly one tool call — call this once per operation. Typical flow: list_models → create_payment → check_payment_status → call tool. The invoice ...

Risk signalsHigh parameter count (12 properties)

Part of the Sats4AI - Bitcoin-Powered AI Tools server.

create_payment can move real money through Sats4AI - Bitcoin-Powered AI Tools, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SATS4AI - BITCOIN-POWERED AI TOOLS →

Free to start. No card required.

AI agents use create_payment to initiate financial transactions through Sats4AI - Bitcoin-Powered AI Tools. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

create_payment moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_payment": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

See the full Sats4AI - Bitcoin-Powered AI Tools policy for all 49 tools.

Get this rule live on your own Sats4AI - Bitcoin-Powered AI Tools server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SATS4AI - BITCOIN-POWERED AI TOOLS →

View all 49 tools →

These attack patterns abuse exactly the kind of access create_payment gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_payment only ever does what you allow.

SECURE SATS4AI - BITCOIN-POWERED AI TOOLS →

Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the create_payment tool do? +

Create a Lightning invoice to pay for one AI service call. Returns JSON: { paymentId, invoice (BOLT11), amount (sats), expiresAt }. Each payment covers exactly one tool call — call this once per operation. Typical flow: list_models → create_payment → check_payment_status → call tool. The invoice expires in 10 minutes. Call list_models first to discover modelId values. modelId is optional — omit it to use the default (best) model. Some tools require extra params at payment time because pricing depends on them: generate_text requires prompt (price = f(char count)); send_sms, place_call, ai_call require phoneNumber; generate_video requires duration, mode, generate_audio; animate_image requires duration (100 sats/sec); edit_image requires resolution (1K=200, 2K=300, 4K=450 sats). If required params are missing, the response includes an error with the missing field names.. It is categorised as a Financial tool in the Sats4AI - Bitcoin-Powered AI Tools MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on create_payment? +

Register the Sats4AI - Bitcoin-Powered AI Tools MCP server in PolicyLayer and add a rule for create_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 Sats4AI - Bitcoin-Powered AI Tools. Nothing to install.

What risk level is create_payment? +

create_payment 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 create_payment? +

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

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

create_payment is provided by the Sats4AI - Bitcoin-Powered AI Tools MCP server (cnghockey/sats4ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sats4AI - Bitcoin-Powered AI Tools tool call.

Deterministic rules across all 49 Sats4AI - Bitcoin-Powered AI Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.