rotate_api_key
Generate a new API key, invalidating the old one. For operators: triggers 60-min withdrawal cooldown. For agents: 30-min cooldown.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/rotate-api-key.md
What rotate_api_key does on Lightning Wallet
AI agents use rotate_api_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 rotate_api_key is rated Medium
The tool creates a new API key and invalidates the old one, which is a reversible credential rotation operation. While it does trigger cooldown periods that temporarily restrict withdrawals, the core action is credential management (Write), not a financial transaction or permanent deletion.
From the tool's definition Tool description states 'Generate a new API key, invalidating the old one' and 'triggers 60-min withdrawal cooldown' for operators and '30-min cooldown' for agents. This modifies authentication credentials and wallet access state.
Attacks that exploit this kind of access
The rule that runs rotate_api_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 rotate_api_key, this is the rule to start with:
rotate_api_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 rotate_api_key call is checked against it from then on.
Questions about rotate_api_key
Generate a new API key, invalidating the old one. For operators: triggers 60-min withdrawal cooldown. For agents: 30-min cooldown. 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 rotate_api_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.
rotate_api_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 rotate_api_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 rotate_api_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.
rotate_api_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