zap-wallet-set
Set the NWC wallet URI for the active identity. Each persona can have its own Lightning wallet.
This record as markdown: /tools/dev-forgesworn-bray/zap-wallet-set.md
What zap-wallet-set does on Nostr Bray
AI agents use zap-wallet-set to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why zap-wallet-set is rated Medium
This tool modifies a critical financial configuration — the NWC (Nostr Wallet Connect) URI that links an identity to a Lightning wallet. While it doesn't directly move money, setting or overwriting this URI could redirect all future zap/payment flows to an attacker-controlled wallet, making it a high-severity Write operation with near-Financial implications.
From the tool's definition 'Set the NWC wallet URI for the active identity' and 'Each persona can have its own Lightning wallet'
Attacks that exploit this kind of access
The rule that runs zap-wallet-set 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-wallet-set, this is the rule to start with:
zap-wallet-set 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every zap-wallet-set call is checked against it from then on.
Questions about zap-wallet-set
Set the NWC wallet URI for the active identity. Each persona can have its own Lightning wallet. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for zap-wallet-set: 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.
zap-wallet-set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zap-wallet-set 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 zap-wallet-set. 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.
zap-wallet-set 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.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue