wait_for
Wait for specific conditions
Part of the Chrome DevTools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents invoke wait_for to trigger processes or run actions in Chrome DevTools. 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.
WHY ENFORCE A POLICY ON WAIT_FOR
wait_for 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.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
wait_for:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Chrome DevTools policy for all 29 tools.
DETAILS
MORE CHROME DEVTOOLS TOOLS
navigate_page Execute new_page Execute select_page Execute close_page Execute evaluate_script Execute performance_start_trace Execute performance_stop_trace Execute list_pages Read SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the wait_for tool do?
Wait for specific conditions. It is categorised as a Execute tool in the Chrome DevTools 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?
Add a rule in your Intercept YAML policy under the tools section for wait_for. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome DevTools MCP server.
What risk level is wait_for?
wait_for is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit wait_for?
Yes. Add a rate_limit block to the wait_for 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 completely?
Set action: deny in the Intercept 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.
What MCP server provides wait_for?
wait_for is provided by the Chrome DevTools MCP server (ChromeDevTools/chrome-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON CHROME DEVTOOLS
Open source. One binary. Zero dependencies.