// MCP TOOL REFERENCE

CHROME DEBUG MCP SERVER TOOLS

10 tools from the Chrome Debug MCP Server MCP Server, categorised by risk level.

View the Chrome Debug MCP Server policy →

// ALL 10 CHROME DEBUG MCP SERVER TOOLS

READ 1 tools

Read get_page_content 获取当前页面的HTML内容

DESTRUCTIVE 1 tools

Destructive close_browser 关闭浏览器连接

EXECUTE 8 tools

Execute launch_browser 启动浏览器连接，连接到Chrome调试端口以保持登录状态 Execute navigate_to 导航到指定URL，智能管理标签页（相同域名复用标签页） Execute click 在指定坐标位置点击 Execute hover 将鼠标悬停在指定坐标位置 Execute resize_browser 调整浏览器窗口大小 Execute scroll_down 向下滚动页面一个视口高度 Execute scroll_up 向上滚动页面一个视口高度 Execute type_text 输入文本内容

// FAQ

How many tools does the Chrome Debug MCP Server MCP server have? +

The Chrome Debug MCP Server MCP server exposes 10 tools across 3 categories: Read, Destructive, Execute.

How do I enforce policies on Chrome Debug MCP Server tools? +

Route the Chrome Debug MCP Server 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 Chrome Debug MCP Server tools fall into? +

Chrome Debug MCP Server tools are categorised as Read (1), Destructive (1), Execute (8). Each category has a recommended default policy.

Enforce policy on every Chrome Debug MCP Server tool call.

Start from Chrome Debug MCP Server, 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.