import_wallet · Neo N3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_wallet does on Neo N3 MCP Server

AI agents use import_wallet to create or update resources in Neo N3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neo N3 MCP Server environment.

WHY IT NEEDS A POLICY

Why import_wallet needs a policy

This tool creates new wallet entries in the system, which is a reversible data modification (Write category). While it doesn't directly move funds, it establishes control over blockchain assets by importing private key material. The severity is high because a compromised tool could allow an attacker to import malicious wallets and subsequently use sibling tools like 'transfer_assets' or 'claim_gas' to move funds.

From the tool's definition The tool 'import_wallet' creates or modifies wallet state by importing a wallet from a private key or WIF format, returning an address and optionally encrypted WIF. This is a write operation that persists wallet data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_wallet Rate-limited

import_wallet 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": {
    "import_wallet": {
      "limits": [
        {
          "counter": "import_wallet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Neo N3 MCP Server, so you can run agents against it safely.

FAQ

Questions about import_wallet

What does the import_wallet tool do? +

Import a Neo N3 wallet from private key or WIF. Returns address and optionally encrypted WIF. It is categorised as a Write tool in the Neo N3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_wallet? +

Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for import_wallet: 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 Neo N3 MCP Server. Nothing to install.

What risk level is import_wallet? +

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

Can I rate-limit import_wallet? +

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

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

import_wallet is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.