7 tools. 6 can modify or destroy data without limits.
6 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (browsercat_click, browsercat_fill, browsercat_hover) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (browsercat_evaluate, browsercat_navigate) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
browsercat_click:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
browsercat_screenshot:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The BrowserCat Remote Browser Automation server has 4 write tools including browsercat_click, browsercat_fill, browsercat_hover. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
7 tools across 3 categories: Execute, Read, Write. 1 are read-only. 6 can modify, create, or delete data.
One line change. Instead of running the BrowserCat Remote Browser Automation server directly, prefix it with Intercept: intercept -c pipethedev-browsercat-mcp-server.yaml -- npx -y @pipethedev/browsercat-mcp-server. Download a pre-built policy from policylayer.com/policies/pipethedev-browsercat-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.