crow_browser_wait_for_user

Pause automation and display a message. Waits until the user signals to continue (call again with resume=true).

SERVERCrow SOURCEkh0pper/crow

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-browser-wait-for-user.md

WHAT IT DOES

What crow_browser_wait_for_user does on Crow

AI agents invoke crow_browser_wait_for_user to trigger actions in Crow. 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.

RISK

Why crow_browser_wait_for_user is rated High

This tool pauses and resumes automation workflows, controlling browser behavior and execution flow. While not destructive or financial, it executes operations that affect system state and automation flow. The ability to pause/resume browser automation and trigger user interactions makes it an Execute category tool.

From the tool's definition Tool name includes 'wait_for_user' and description states 'Pause automation and display a message. Waits until the user signals to continue', indicating it triggers external browser operations and state changes that depend on user interaction arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_browser_wait_for_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_browser_wait_for_user, this is the rule to start with:

crow_browser_wait_for_user Rate-limited

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_browser_wait_for_user call is checked against it from then on.

FAQ

Questions about crow_browser_wait_for_user

What does the crow_browser_wait_for_user tool do? +

Pause automation and display a message. Waits until the user signals to continue (call again with resume=true). It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on crow_browser_wait_for_user? +

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

What risk level is crow_browser_wait_for_user? +

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

Can I rate-limit crow_browser_wait_for_user? +

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

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

crow_browser_wait_for_user is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools → High-risk tools on this server →

Across the catalogue

browser_wait_for_element on Percepta MCP Server →wait_for_renders on Why Did You Render →qt_wait_for on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →