Wait for a transaction to be confirmed (mined). Polls the network until confirmation.
AI agents call wait_for_transaction to retrieve information from EVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only monitors/polls the blockchain network to check transaction status until it is confirmed. It does not initiate any transaction, move funds, or modify any state — it is purely a read/observation operation. The polling itself has no side effects on the blockchain.
From the tool's definition Wait for a transaction to be confirmed (mined). Polls the network until confirmation.
Documented attack patterns abuse exactly the kind of access wait_for_transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wait_for_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_transaction": {}
}
} wait_for_transaction is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Wait for a transaction to be confirmed (mined). Polls the network until confirmation. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM 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 EVM MCP Server. Nothing to install.
wait_for_transaction is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
wait_for_transaction is provided by the EVM MCP Server MCP server (mcpdotdirect/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EVM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 EVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.