Wait until specific text appears (or disappears with gone=true) in the page body. Unlike wait_for_element (CSS selector), this waits for visible text content — useful for checking AJAX responses, form submission results, loading spinners, or any dynamic text.
AI agents invoke wait_for_text to trigger actions in MacWright. 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.
This tool executes a wait-and-check operation that blocks until a condition is met, allowing an AI agent to control program flow based on dynamic content. While not directly destructive or financial, it enables sequential execution of browser automation tasks. An agent could use it to wait for confirmation messages before proceeding with further actions, or to detect when a process completes.
From the tool's definition The tool waits for text to appear/disappear in page content, handling dynamic changes like AJAX responses and form submission results. It triggers conditional logic based on observable UI state changes, which constitutes control flow execution.
Attacks that exploit this kind of access
Wait until specific text appears (or disappears with gone=true) in the page body. Unlike wait_for_element (CSS selector), this waits for visible text content — useful for checking AJAX responses, form submission results, loading spinners, or any dynamic text. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MacWright MCP server in PolicyLayer and add a rule for wait_for_text: 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 MacWright. Nothing to install.
wait_for_text 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_text 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_text. 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_text is provided by the MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →