get_connection_status
Get the current connection status to the browser. Retrieves comprehensive information about the current connection state, including browser details if connected. This is useful for diagnostics and determining whether other operations can be performed. The function provides different information d...
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-connection-status.md
What get_connection_status does on Chrome Devtools
AI agents call get_connection_status to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_connection_status is rated Low
This is a diagnostic/status-checking tool that gathers read-only information about the browser connection. It returns status details such as browser version and connection state but performs no operations that create, modify, delete, or execute code. The description explicitly indicates it is 'useful for diagnostics' and does not change any state.
From the tool's definition Tool name and description indicate it 'Retrieves comprehensive information about the current connection state' with 'no side effects' — it only queries the browser connection status without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_connection_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_connection_status, this is the rule to start with:
get_connection_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every get_connection_status call is checked against it from then on.
Questions about get_connection_status
Get the current connection status to the browser. Retrieves comprehensive information about the current connection state, including browser details if connected. This is useful for diagnostics and determining whether other operations can be performed. The function provides different information depending on connection state: - If connected: Browser version, target info, and connection details - If not connected: Basic status information - If not initialised: Client setup status Returns: Status dictionary containing: - success: Boolean indicating status check success - message: Human-readable status description - data: Status details including: - connected: Boolean connection status - status: Text status (connected/disconnected/not_initialised) - targetInfo: Browser information (if connected) - host: Chrome host address (if connected) - port: Chrome port number (if connected) Note: This function is safe to call at any time and will not modify the connection state, only report it. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_connection_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Chrome Devtools. Nothing to install.
get_connection_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_connection_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_connection_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_connection_status is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
This server
Across the catalogue