waitForConfirmation · Algorand MCP Server MCP: Risk & Policy

WHAT IT DOES

What waitForConfirmation does on Algorand MCP Server

AI agents invoke waitForConfirmation to trigger actions in Algorand 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 waitForConfirmation needs a policy

This is classified as Execute rather than Read because it actively monitors and responds to blockchain confirmation events, which is a form of operational control. While not destructive or financial by itself, it engages with transaction processing logic.

From the tool's definition Tool name 'waitForConfirmation' and description 'Wait for a transaction to be confirmed' indicate the tool monitors/polls blockchain state for transaction finality.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

waitForConfirmation Rate-limited

waitForConfirmation 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": {
    "waitForConfirmation": {
      "limits": [
        {
          "counter": "waitforconfirmation_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 Algorand MCP Server, so you can run agents against it safely.

FAQ

Questions about waitForConfirmation

What does the waitForConfirmation tool do? +

Wait for a transaction to be confirmed. It is categorised as a Execute tool in the Algorand 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 waitForConfirmation? +

Register the Algorand MCP Server MCP server in PolicyLayer and add a rule for waitForConfirmation: 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 Algorand MCP Server. Nothing to install.

What risk level is waitForConfirmation? +

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

Can I rate-limit waitForConfirmation? +

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

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

waitForConfirmation is provided by the Algorand MCP Server MCP server (tairon-ai/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.