marketplace-pay

Pay an L402 invoice via NWC and store credentials for authenticated API calls.

SERVERNostr Bray SOURCEnostr-bray

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-bray/marketplace-pay.md

WHAT IT DOES

What marketplace-pay does on Nostr Bray

AI agents use marketplace-pay to commit financial operations through Nostr Bray, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why marketplace-pay is rated Critical

This tool moves money (Lightning Network payments) and commits financial obligations by processing invoices. It also stores wallet credentials, which amplifies the risk. Financial operations are the most severe category, and the critical severity reflects that an AI agent with access could drain funds or make unauthorized payments if misdirected or compromised.

From the tool's definition Tool name is 'marketplace-pay' and description explicitly states 'Pay an L402 invoice via NWC' — L402 is a Lightning Network payment protocol, and NWC (Nostr Wallet Connect) is a standard for wallet access.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs marketplace-pay safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marketplace-pay, this is the rule to start with:

marketplace-pay Approval-gated

Any call to marketplace-pay is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "marketplace-pay": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every marketplace-pay call is checked against it from then on.

FAQ

Questions about marketplace-pay

What does the marketplace-pay tool do? +

Pay an L402 invoice via NWC and store credentials for authenticated API calls. It is categorised as a Financial tool in the Nostr Bray MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on marketplace-pay? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for marketplace-pay: 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 Nostr Bray. Nothing to install.

What risk level is marketplace-pay? +

marketplace-pay 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 marketplace-pay? +

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

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

marketplace-pay is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nostr Bray, and thousands of servers like it.

This server

All 240 Nostr Bray tools → Critical-risk tools on this server →

Across the catalogue

pay_invoice on Bitcoin MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →