set_operator_key
Switch to a different operator API key for subsequent requests. Use after register_operator to start using the new credentials.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/set-operator-key.md
What set_operator_key does on Lightning Wallet
AI agents use set_operator_key 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_operator_key is rated Medium
This tool modifies credential state, making it a Write operation rather than Read. The severity is high because switching operator keys could allow an agent to redirect financial transactions (Bitcoin/Lightning payments) to different endpoints or operators, potentially causing funds to be sent to an attacker-controlled wallet.
From the tool's definition Tool description states "Switch to a different operator API key for subsequent requests," indicating modification of authentication credentials that will affect subsequent operations.
Attacks that exploit this kind of access
The rule that runs set_operator_key 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_operator_key, this is the rule to start with:
set_operator_key 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_operator_key call is checked against it from then on.
Questions about set_operator_key
Switch to a different operator API key for subsequent requests. Use after register_operator to start using the new credentials. 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_operator_key: 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_operator_key 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_operator_key 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_operator_key. 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_operator_key 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