ToolTrust
C27/100
ChromeDevTools

chrome-devtools-mcp

mcpchrome-devtools-mcp-v1.6.0

@ChromeDevTools

Chrome DevTools for coding agents

By ChromeDevTools | 47 findings | Scanned 7/28/2026 | tooltrust-scanner/v0.3.19 | 47.7k

1 Critical4 Low42 Info

Risk Summary

Needs Approval

Dep Visibility plus Excessive Permissions raises enough risk that this tool should not be auto-trusted.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: Keep this tool behind manual approval and avoid unattended runs until the risky capabilities are narrowed or removed.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (47)

  • CriticalAS-006

    💻Arbitrary Code Execution

    heuristic signal

    evaluate_script:tool name or description implies arbitrary script/code execution (evaluate_script, execute javascript, etc.)

    Fix: This tool can execute arbitrary code or shell commands on the host system. Remove it unless strictly required. If kept: (1) restrict access to trusted users/agents only, (2) require human approval before each invocation (Claude Desktop: set approval_required: true; other clients: enable equivalent confirmation), (3) use the most restrictive sandbox or read-only mode available, and (4) never expose this tool to untrusted input sources.

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×4

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    emulateevaluate_scriptget_network_requestlist_network_requests

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×29

    No metadata.dependencies or repo_url were exposed by this MCP server, and no local project manifest could be inferred from the launch command.

    clickclose_pagedragemulateevaluate_scriptfillfill_formget_console_messageget_network_requesthandle_dialoghoverlighthouse_auditlist_console_messageslist_network_requestslist_pagesnavigate_pagenew_pageperformance_analyze_insightperformance_start_traceperformance_stop_tracepress_keyresize_pageselect_pagetake_heapsnapshottake_screenshottake_snapshottype_textupload_filewait_for

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×13

    declared capabilities: HTTP requests

    emulate

    declared capabilities: code/command execution, filesystem access

    evaluate_script

    declared capabilities: network access, filesystem access

    get_network_request

    declared capabilities: filesystem access

    lighthouse_auditperformance_start_traceperformance_stop_tracetake_heapsnapshottake_screenshottake_snapshotupload_file

    declared capabilities: network access

    list_network_requestsnew_page

    declared capabilities: code/command execution, network access

    navigate_page

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y chrome-devtools-mcp"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade C](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-c.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)