15 tools from the BrowserTools MCP Server, categorised by risk level.
View the BrowserTools policy →getConsoleErrors Retrieve recent console error messages 2/5 getConsoleLogs Retrieve recent browser console log entries 2/5 getNetworkErrors Get failed HTTP requests (4xx/5xx) 2/5 getNetworkLogs Get all XHR/fetch network logs 2/5 getNetworkSuccess Get successful HTTP requests (2xx/3xx) 2/5 getSelectedElement Get currently selected DOM element from DevTools 2/5 takeScreenshot Take a screenshot of the active browser tab 2/5 runAccessibilityAudit Run WCAG accessibility audit via Lighthouse 3/5 runAuditMode Run all audit tools in sequence 4/5 runBestPracticesAudit Run web best-practices audit 3/5 runDebuggerMode Run all debugging tools in sequence 4/5 runNextJSAudit Run Next.js-specific audit 3/5 runPerformanceAudit Run performance audit on the page 3/5 runSEOAudit Run SEO audit on the page 3/5 The BrowserTools MCP server exposes 15 tools across 3 categories: Read, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the BrowserTools server.
BrowserTools tools are categorised as Read (7), Destructive (1), Execute (7). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept