Wait for an element to appear in the AX tree. Polls the tree every 500ms until the element is found or timeout is reached. Use after clicks or navigation that trigger async content loading (SPAs, AJAX).\n\nExamples:\n wait results_list Wait for search results\n wait submit_btn --type button Wait ...
Risk signalsBulk/mass operation — affects multiple targets
Part of the DOMShell server.
Free to start. No card required.
AI agents invoke domshell_wait to trigger processes or run actions in DOMShell. 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.
domshell_wait can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"domshell_wait": {
"limits": [
{
"counter": "domshell_wait_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full DOMShell policy for all 38 tools.
These attack patterns abuse exactly the kind of access domshell_wait gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Wait for an element to appear in the AX tree. Polls the tree every 500ms until the element is found or timeout is reached. Use after clicks or navigation that trigger async content loading (SPAs, AJAX).\n\nExamples:\n wait results_list Wait for search results\n wait submit_btn --type button Wait for a button to appear\n wait loading_spinner --timeout 10 Wait up to 10 seconds. It is categorised as a Execute tool in the DOMShell MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DOMShell MCP server in PolicyLayer and add a rule for domshell_wait: 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 DOMShell. Nothing to install.
domshell_wait 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 domshell_wait 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 domshell_wait. 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.
domshell_wait is provided by the DOMShell MCP server (@apireno/domshell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 DOMShell tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.