zap-list-transactions

List recent Lightning transactions via NWC.

SERVERNostr Bray SOURCEnostr-bray

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-bray/zap-list-transactions.md

WHAT IT DOES

What zap-list-transactions does on Nostr Bray

AI agents call zap-list-transactions to retrieve information from Nostr Bray without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zap-list-transactions is rated Low

This tool queries and retrieves transaction history via Nostr Wallet Connect (NWC). It does not initiate payments, modify wallet state, or execute financial operations—it only reads transaction records. While the data is financial in nature, the operation itself is a passive read with no side effects or ability to move funds.

From the tool's definition Tool name uses 'list' (passive retrieval verb) and description states 'List recent Lightning transactions' — a query operation that retrieves historical data without modification or execution of payments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zap-list-transactions 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 zap-list-transactions, this is the rule to start with:

zap-list-transactions Allowed

zap-list-transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zap-list-transactions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about zap-list-transactions

What does the zap-list-transactions tool do? +

List recent Lightning transactions via NWC. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zap-list-transactions? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for zap-list-transactions: 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 zap-list-transactions? +

zap-list-transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zap-list-transactions? +

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

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

zap-list-transactions 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 →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →