wait_for
Wait for the specified text to appear on the selected page.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/wait-for.md
What wait_for does on Chrome DevTools MCP
AI agents invoke wait_for to trigger actions in Chrome DevTools MCP. 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 wait_for is rated High
This tool does not retrieve data (Read), create/modify reversibly (Write), delete irreversibly (Destructive), or move money (Financial). However, it is a blocking operation that controls browser execution flow and can affect timing of subsequent automated actions.
From the tool's definition Tool description states it 'wait[s] for the specified text to appear on the selected page,' which requires active monitoring and blocking execution flow.
Attacks that exploit this kind of access
The rule that runs wait_for safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wait_for, this is the rule to start with:
wait_for 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome DevTools MCP, apply this rule, and every wait_for call is checked against it from then on.
Questions about wait_for
Wait for the specified text to appear on the selected page. It is categorised as a Execute tool in the Chrome DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome DevTools MCP server in PolicyLayer and add a rule for wait_for: 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 Chrome DevTools MCP. Nothing to install.
wait_for is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for 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. 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 is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome DevTools, and thousands of servers like it.
Across the catalogue