lightning_unlock
Unlock the Lightning wallet for the current session. Required before
This record as markdown: /tools/io-github-aibtcdev-mcp-server/lightning-unlock.md
What lightning_unlock does on Aibtc
AI agents invoke lightning_unlock to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why lightning_unlock is rated High
Unlocking a Lightning wallet initiates an authenticated session granting access to financial operations (payments, channel management, etc.). The description is truncated, but unlocking a crypto wallet is an Execute-level action that enables subsequent financial operations. It does not directly move funds, but it enables high-severity financial actions.
From the tool's definition Unlock the Lightning wallet for the current session. Required before
Attacks that exploit this kind of access
The rule that runs lightning_unlock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lightning_unlock, this is the rule to start with:
lightning_unlock stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every lightning_unlock call is checked against it from then on.
Questions about lightning_unlock
Unlock the Lightning wallet for the current session. Required before. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aibtc MCP server in PolicyLayer and add a rule for lightning_unlock: 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 Aibtc. Nothing to install.
lightning_unlock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lightning_unlock 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 lightning_unlock. 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.
lightning_unlock is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue