DOMShell

38 tools. 16 can modify or destroy data without limits.

16 write tools that can modify data. Rate limits recommended.

Last updated:

16 can modify or destroy data
22 read-only
38 tools total

16 DOMShell tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DOMSHELL →

Free to start. No card required.

Read (22) Write / Execute (16) Destructive / Financial (0)

Write operations (domshell_call, domshell_click, domshell_close) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (domshell_each, domshell_execute, domshell_js) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Rate limit write operations
{
  "domshell_call": {
    "limits": [
      {
        "counter": "domshell_call_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "domshell_back": {
    "limits": [
      {
        "counter": "domshell_back_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Get this policy live on your own DOMShell server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY DOMSHELL →
How do I prevent bulk modifications through DOMShell? +

The DOMShell server has 10 write tools including domshell_call, domshell_click, domshell_close. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach DOMShell.

How many tools does the DOMShell MCP server expose? +

38 tools across 3 categories: Execute, Read, Write. 22 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on DOMShell? +

Register the DOMShell MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every DOMShell tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.