update_operator
Update operator profile: set your email (sends a verification link - required for the free-sats promo) and/or display name. REQUIRES OPERATOR KEY.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/update-operator.md
What update_operator does on Lightning Wallet
AI agents use update_operator 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 update_operator is rated Medium
This tool modifies user profile data (email, display name) reversibly. It does not delete data (so not Destructive), does not move money directly (so not Financial), and does not execute arbitrary code or external operations (so not Execute). The 'REQUIRES OPERATOR KEY' restriction mitigates risk but does not change the fundamental category.
From the tool's definition Tool description states 'Update operator profile: set your email...and/or display name.' The words 'Update' and 'set' indicate data modification. The mention of email verification and promo eligibility shows this creates reversible state changes.
Attacks that exploit this kind of access
The rule that runs update_operator 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 update_operator, this is the rule to start with:
update_operator 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 update_operator call is checked against it from then on.
Questions about update_operator
Update operator profile: set your email (sends a verification link - required for the free-sats promo) and/or display name. REQUIRES OPERATOR 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 update_operator: 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.
update_operator 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 update_operator 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 update_operator. 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.
update_operator 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