High Risk →

wait_for_transaction

Wait for transaction confirmation (polls until mined).

Part of the Kosyak Evm MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

kosyak-evm-mcp-server Execute Risk 3/5

AI agents invoke wait_for_transaction to trigger processes or run actions in Kosyak Evm. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

wait_for_transaction can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

kosyak-evm.yaml
tools:
  wait_for_transaction:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Kosyak Evm policy for all 43 tools.

Tool Name wait_for_transaction
Category Execute
Risk Level High

View all 43 tools →

Agents calling execute-class tools like wait_for_transaction have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

wait_for_transaction is one of the high-risk operations in Kosyak Evm. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the wait_for_transaction tool do? +

Wait for transaction confirmation (polls until mined).. It is categorised as a Execute tool in the Kosyak Evm 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? +

Add a rule in your Intercept YAML policy under the tools section for wait_for_transaction. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kosyak Evm MCP server.

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 Intercept 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 Intercept 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 Kosyak Evm MCP server (kosyak-evm-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kosyak Evm

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.