15 tools. 8 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Free to start. No card required.
Destructive tools (wipeLogs) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Execute tools (runAccessibilityAudit, runAuditMode, runBestPracticesAudit) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
{
"wipeLogs": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"getConsoleErrors": {
"limits": [
{
"counter": "getconsoleerrors_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The BrowserTools server exposes 1 destructive tools including wipeLogs. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
15 tools across 3 categories: Destructive, Execute, Read. 7 are read-only. 8 can modify, create, or delete data.
Register the BrowserTools 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.
Starter policies for each. Same risk classification, live on your fleet in minutes.
Deterministic rules across all 15 BrowserTools 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.