wallet_lock

Lock 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-lock.md

WHAT IT DOES

What wallet_lock does on Aibtc

AI agents invoke wallet_lock 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_lock is rated High

Locking a wallet/agent is an operational action that changes system state (prevents further transactions or access). It is not a simple read, and while potentially reversible (unlock), it triggers an external operation affecting agent/wallet functionality. Given the financial context (sibling tools include swap, order creation), locking could disrupt ongoing financial operations.

From the tool's definition 'Lock the agent' — the tool name 'wallet_lock' combined with the description suggests locking a wallet or agent session, triggering an external state change

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wallet_lock Rate-limited

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

FAQ

Questions about wallet_lock

What does the wallet_lock tool do? +

Lock 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_lock? +

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

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

Can I rate-limit wallet_lock? +

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

Set action: deny in the PolicyLayer policy for wallet_lock. 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_lock? +

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