// SCAN REPORT

Neo N3 MCP Server

27 tools. 9 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

9 can modify or destroy data

18 read-only

27 tools total

Community server · catalogue entry verified 29/06/2026

How to control Neo N3 MCP Server ↓

TOOL MAP

What Neo N3 MCP Server exposes to your agents

Read (18) Write / Execute (7) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Neo N3 MCP Server tools

Financial · Critical transfer_assets This tool directly moves digital assets (NEP-17 tokens, which represent value on the Neo N3 blockchain) from one address to another. Financial · High claim_gas Claiming GAS is a financial operation that moves/commits cryptocurrency assets to an account on the Neo N3 blockchain. Execute · High deploy_contract Contract deployment is an Execute action: it runs code (the smart contract) on an external system (Neo N3 blockchain) with effects dependent on the contract's logic. Execute · High invoke_contract This tool executes arbitrary smart contract methods on the Neo N3 blockchain.

9 of Neo N3 MCP Server's 27 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Neo N3 MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Neo N3 MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "claim_gas": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "create_wallet": {
    "limits": [
      {
        "counter": "create_wallet_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "estimate_invoke_fees": {
    "limits": [
      {
        "counter": "estimate_invoke_fees_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Neo N3 MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NEO N3 →

Instant setup, no code required.

FULL CATALOGUE

All 27 Neo N3 MCP Server tools

FINANCIAL 2 tools

Financial claim_gas Claim available GAS for an account. Requires account WIF. Financial transfer_assets Transfer NEP-17 assets between addresses. Requires sender WIF.

EXECUTE 3 tools

Execute deploy_contract Deploy a smart contract from a NEF script and manifest. Requires deployer WIF and explicit confirmation. Execute invoke_contract Prepare invocation details for a smart contract method. Accepts either a scriptHash or a generic contract refe Execute wait_for_transaction Poll until a transaction is confirmed or a timeout is reached

WRITE 4 tools

Write create_wallet Create a new Neo N3 wallet (address and encrypted WIF) Write import_wallet Import a Neo N3 wallet from private key or WIF. Returns address and optionally encrypted WIF. Write neofs_create_container [NeoFS] Create a new storage container (requires WIF) Write set_network_mode Set the network mode (mainnet_only, testnet_only, both). Requires restart.

READ 18 tools

Read estimate_invoke_fees Estimate network and system fees for a contract invocation by script hash or a generic contract reference Read estimate_transfer_fees Estimate network and system fees for a transfer transaction Read get_application_log Get the application log for a confirmed transaction Read get_balance Get native (NEO/GAS) and NEP-17 token balances for an address Read get_block Get block details by height or hash Read get_block_count Get the current block height of the Neo N3 blockchain Read get_blockchain_info Get essential blockchain information (block height, version) Read get_contract_info Get details about a contract by known name, script hash, or Neo address Read get_contract_status Check whether a contract is deployed and inspect its current on-chain status by known name, script hash, or Ne Read get_nep11_balances Get NEP-11 balances for an address with additive asset enrichment when available Read get_nep11_transfers Get NEP-11 transfer history for an address with additive asset and party enrichment when available Read get_nep17_transfers Get NEP-17 transfer history for an address with additive known-account enrichment when available Read get_network_mode Get the currently configured network mode (mainnet_only, testnet_only, both) Read get_transaction Get transaction details by hash Read get_unclaimed_gas Get the currently unclaimed GAS amount for an address Read get_wallet Get sanitized metadata for a stored wallet by address. Read list_famous_contracts List known famous contracts with their names and script hashes for the active network(s) Read neofs_get_containers [NeoFS] List containers owned by an address

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Neo N3 MCP Server

Can an AI agent move money through the Neo N3 MCP Server MCP server? +

Yes. The Neo N3 MCP Server server exposes 2 financial tools including claim_gas, transfer_assets. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Neo N3 MCP Server? +

The Neo N3 MCP Server server has 4 write tools including create_wallet, import_wallet, neofs_create_container. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Neo N3 MCP Server.

How many tools does the Neo N3 MCP Server MCP server expose? +

27 tools across 4 categories: Execute, Financial, Read, Write. 18 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Neo N3 MCP Server? +

Register the Neo N3 MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Neo N3 MCP Server tool call.

Deterministic rules across all 27 Neo N3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NEO N3 →

Instant setup, no code required.

27 Neo N3 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.