Wait for text to appear, disappear, or a specified time to pass.
AI agents invoke browser_wait_for to trigger actions in Camoufox. 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.
browser_wait_for is a synchronization primitive for browser automation that can block execution and monitor page state changes. While waiting itself is not inherently destructive, it enables conditional logic in sequences of browser actions (click, form fill, navigation) whose effects depend on external website behavior.
From the tool's definition Tool performs browser automation actions that trigger external operations and side effects (waiting for DOM changes, monitoring page state).
Documented attack patterns abuse exactly the kind of access browser_wait_for gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_wait_for:
{
"version": "1",
"default": "deny",
"tools": {
"browser_wait_for": {
"limits": [
{
"counter": "browser_wait_for_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_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.
Free to start. No card required.
Wait for text to appear, disappear, or a specified time to pass. It is categorised as a Execute tool in the Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Camoufox MCP server in PolicyLayer and add a rule for browser_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 Camoufox. Nothing to install.
browser_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 browser_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 browser_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.
browser_wait_for is provided by the Camoufox MCP server (rlgrpe/camoufox-mcp-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Camoufox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.