wallet_create
Create a new wallet for the agent with a generated BIP39 24-word mnemonic. The wallet is encrypted locally and stored in ~/.aibtc/. IMPORTANT: Save the mnemonic securely - it will only be shown once!
This record as markdown: /tools/io-github-aibtcdev-mcp-server/wallet-create.md
What wallet_create does on Aibtc
AI agents use wallet_create 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.
Why wallet_create is rated Medium
This tool creates and persists new cryptographic wallet state (mnemonic + encrypted wallet). While creation is technically reversible (the wallet file could be deleted), the mnemonic's one-time display means losing it makes the wallet inaccessible—functionally destructive. However, the primary action is 'Create', making it Write rather than Destructive.
From the tool's definition Tool creates a new wallet with a generated BIP39 24-word mnemonic and stores it in ~/.aibtc/. The description explicitly states 'Create a new wallet' and emphasizes that the mnemonic 'will only be shown once', indicating irreversible state creation.
Attacks that exploit this kind of access
The rule that runs wallet_create 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_create, this is the rule to start with:
wallet_create 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 Aibtc, apply this rule, and every wallet_create call is checked against it from then on.
Questions about wallet_create
Create a new wallet for the agent with a generated BIP39 24-word mnemonic. The wallet is encrypted locally and stored in ~/.aibtc/. IMPORTANT: Save the mnemonic securely - it will only be shown once!. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for wallet_create: 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.
wallet_create 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 wallet_create 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 wallet_create. 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.
wallet_create 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.
This server
Across the catalogue