Run a command across multiple open tabs. Iterates over all non-chrome tabs (optionally filtered by title/URL pattern), switches into each, runs the command, and collects results. Restores the original tab when done.\n\nOptions:\n --pattern FILTER Only tabs whose title or URL contains FILTER\n --l...
Risk signalsBulk/mass operation — affects multiple targets
Part of the DOMShell server.
Free to start. No card required.
AI agents invoke domshell_each 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_each 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_each": {
"limits": [
{
"counter": "domshell_each_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_each 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.
Run a command across multiple open tabs. Iterates over all non-chrome tabs (optionally filtered by title/URL pattern), switches into each, runs the command, and collects results. Restores the original tab when done.\n\nOptions:\n --pattern FILTER Only tabs whose title or URL contains FILTER\n --limit N Process at most N matching tabs\n\nExamples:\n each eval document.title Title from every tab\n each --pattern wiki eval document.title Only Wikipedia tabs\n each --pattern wiki --limit 3 eval document.title First 3 Wikipedia tabs. 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_each: 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_each 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_each 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_each. 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_each 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.