invoke_contract · Neo N3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What invoke_contract does on Neo N3 MCP Server

AI agents invoke invoke_contract to trigger actions in Neo N3 MCP Server. 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.

WHY IT NEEDS A POLICY

Why invoke_contract needs a policy

This tool executes arbitrary smart contract methods on the Neo N3 blockchain. While it can perform read-only queries (lower risk), it also prepares write transactions when a private key (fromWIF) is provided, which can modify blockchain state and execute arbitrary contract logic.

From the tool's definition The tool 'invoke_contract' can execute smart contract methods with the capability to prepare write transactions when 'fromWIF is provided'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

invoke_contract Rate-limited

invoke_contract 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": {
    "invoke_contract": {
      "limits": [
        {
          "counter": "invoke_contract_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 invoke_contract

What does the invoke_contract tool do? +

Prepare invocation details for a smart contract method. Accepts either a scriptHash or a generic contract reference such as a known name, script hash, or Neo address. If fromWIF is provided, prepares a write transaction; otherwise, performs a read-only query. It is categorised as a Execute tool in the Neo N3 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on invoke_contract? +

Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for invoke_contract: 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 invoke_contract? +

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

Can I rate-limit invoke_contract? +

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

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

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