wallet_unlock

Unlock the agent

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

High RISK CLASS

Category Execute

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-unlock.md

WHAT IT DOES

What wallet_unlock does on Aibtc

AI agents invoke wallet_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.

RISK

Why wallet_unlock is rated High

Unlocking a wallet or agent likely grants access to cryptographic keys and financial operations (given sibling tools like alex_swap, bitflow_create_order). This is an Execute-level action with high blast radius since it enables subsequent financial/destructive operations. The vague description lowers confidence slightly, but the wallet context and financial sibling tools suggest significant risk.

From the tool's definition 'Unlock the agent' - the tool name 'wallet_unlock' combined with the description suggests it triggers an authentication or authorization action on a wallet/agent

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wallet_unlock Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wallet_unlock": {
      "limits": [
        {
          "counter": "wallet_unlock_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_unlock call is checked against it from then on.

FAQ

Questions about wallet_unlock

What does the wallet_unlock tool do? +

Unlock the agent. 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.

How do I enforce a policy on wallet_unlock? +

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

What risk level is wallet_unlock? +

wallet_unlock is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wallet_unlock? +

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

How do I block wallet_unlock completely? +

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

What MCP server provides wallet_unlock? +

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

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →