wallet_import

Import an existing wallet for the agent using a BIP39 mnemonic phrase. The wallet is encrypted locally and stored in ~/.aibtc/.

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/wallet-import.md

WHAT IT DOES

What wallet_import does on Aibtc

AI agents use wallet_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 wallet_import is rated Medium

This tool creates/stores wallet data (Write category), which is reversible in nature. However, it handles sensitive cryptographic credentials (mnemonic phrases), making it high severity due to potential for compromise if misused by an agent. The Write category is most appropriate because the action is storing data rather than executing arbitrary code or causing irreversible deletion.

From the tool's definition Tool name is 'wallet_import' and description states it 'Import an existing wallet' and 'stored in ~/.aibtc/'. Creates or modifies local wallet data by storing encrypted credentials.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wallet_import Rate-limited

wallet_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": {
    "wallet_import": {
      "limits": [
        {
          "counter": "wallet_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 wallet_import call is checked against it from then on.

FAQ

Questions about wallet_import

What does the wallet_import tool do? +

Import an existing wallet for the agent using a BIP39 mnemonic phrase. The wallet is encrypted locally and stored in ~/.aibtc/. 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 wallet_import? +

Register the Aibtc MCP server in PolicyLayer and add a rule for wallet_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 wallet_import? +

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

Can I rate-limit wallet_import? +

Yes. Add a rate_limit block to the wallet_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 wallet_import completely? +

Set action: deny in the PolicyLayer policy for wallet_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 wallet_import? +

wallet_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 →