wait_for_transaction · Neo N3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What wait_for_transaction does on Neo N3 MCP Server

AI agents invoke wait_for_transaction 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 wait_for_transaction needs a policy

This tool executes an external operation—polling a blockchain for transaction confirmation. While it doesn't directly modify state, it performs a blocking operation that depends on transaction arguments and could fail or timeout based on network conditions.

From the tool's definition Tool polls blockchain state based on transaction confirmation logic; involves external operation (blockchain query/wait) whose behavior and duration depend on transaction arguments; similar in risk profile to polling operations that trigger side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_transaction Rate-limited

wait_for_transaction 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": {
    "wait_for_transaction": {
      "limits": [
        {
          "counter": "wait_for_transaction_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 wait_for_transaction

What does the wait_for_transaction tool do? +

Poll until a transaction is confirmed or a timeout is reached. 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 wait_for_transaction? +

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

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

Can I rate-limit wait_for_transaction? +

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

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

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