// MCP TOOL REFERENCE

BROWSER CONNECT TOOLS

16 tools from the Browser Connect MCP Server, categorised by risk level.

View the Browser Connect policy →
// ALL 16 BROWSER CONNECT TOOLS
READ 10 tools
Read network_performance Get network performance statistics for a connected browser tab Read backend_logs_stream Stream and search logs from backend applications (files, processes, Docker containers) Read browser_list_tabs List all available browser tabs that can be connected to Read console_advanced_search Advanced console search with pattern matching, correlation, and statistics Read console_search Search and filter console messages from connected browser tabs Read error_correlate Automatically correlate errors between console and network, find root causes Read log_analyze Intelligently analyze logs to find patterns, anomalies, trends, and suggestions Read network_analyze Analyze network requests and responses from connected browser tabs Read security_scan Scan for security vulnerabilities in console and network traffic Read network_export_har Export network traffic to HAR (HTTP Archive) format
EXECUTE 5 tools
Execute browser_launch Launch a new browser instance with debugging enabled Execute performance_profile Advanced performance profiling with bottleneck detection and recommendations Execute debug_localhost Launch browser with a localhost URL and automatically connect for debugging Execute backend_debugger_attach Attach to a Node.js process debugger for breakpoint debugging Execute browser_connect Connect to a specific browser tab for debugging
OTHER 1 tools
Other browser_disconnect Disconnect from a specific browser tab

Route Browser Connect through PolicyLayer and every one of its 16 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the Browser Connect MCP server have? +

The Browser Connect MCP server exposes 16 tools across 3 categories: Read, Execute, Other.

How do I enforce policies on Browser Connect tools? +

Route the Browser Connect server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Browser Connect tools fall into? +

Browser Connect tools are categorised as Read (10), Execute (5), Other (1). Each category has a recommended default policy.

Enforce policy on every Browser Connect tool call.

Start from Browser Connect, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,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.