set_nostr_identity
Set a Nostr identity for the agent. Stores the private key and derives the public key. REQUIRES AGENT KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/set-nostr-identity.md
What set_nostr_identity does on Lightning Wallet
AI agents use set_nostr_identity to create or update resources in Lightning Wallet, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lightning Wallet environment.
Why set_nostr_identity is rated Medium
This tool creates and modifies identity data (Nostr private/public key pair) in persistent storage. While it doesn't directly move money, it establishes cryptographic credentials that could authorize subsequent financial transactions on the Lightning Wallet server.
From the tool's definition Tool "stores the private key" and "derives the public key", indicating it creates and persists cryptographic identity material. The requirement for AGENT KEY suggests credential management.
Attacks that exploit this kind of access
The rule that runs set_nostr_identity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_nostr_identity, this is the rule to start with:
set_nostr_identity 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 Lightning Wallet, apply this rule, and every set_nostr_identity call is checked against it from then on.
Questions about set_nostr_identity
Set a Nostr identity for the agent. Stores the private key and derives the public key. REQUIRES AGENT KEY. It is categorised as a Write tool in the Lightning Wallet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for set_nostr_identity: 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 Lightning Wallet. Nothing to install.
set_nostr_identity 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 set_nostr_identity 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 set_nostr_identity. 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.
set_nostr_identity is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lightning Wallet, and thousands of servers like it.
This server
Across the catalogue