lightning_import

Import an existing Lightning wallet into the embedded Spark-backed

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/lightning-import.md

WHAT IT DOES

What lightning_import does on Aibtc

AI agents use lightning_import to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.

RISK

Why lightning_import is rated Medium

The tool imports (creates/establishes) a Lightning wallet within an embedded wallet system. This is a Write operation—it modifies local wallet state and creates a connection to the user's existing Lightning wallet, but it is reversible (the import can be undone or overwritten). It is not Destructive since the original wallet is not deleted, nor Financial since it merely imports credentials rather than moving funds.

From the tool's definition Tool name 'lightning_import' and description 'Import an existing Lightning wallet into the embedded Spark-backed' indicate a wallet import operation that creates or modifies data (wallet state) in a local system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lightning_import 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_import, this is the rule to start with:

lightning_import Rate-limited

lightning_import 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lightning_import": {
      "limits": [
        {
          "counter": "lightning_import_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every lightning_import call is checked against it from then on.

FAQ

Questions about lightning_import

What does the lightning_import tool do? +

Import an existing Lightning wallet into the embedded Spark-backed. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lightning_import? +

Register the Aibtc MCP server in PolicyLayer and add a rule for lightning_import: 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.

What risk level is lightning_import? +

lightning_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lightning_import? +

Yes. Add a rate_limit block to the lightning_import 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.

How do I block lightning_import completely? +

Set action: deny in the PolicyLayer policy for lightning_import. 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.

What MCP server provides lightning_import? +

lightning_import 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →