LeashIndex Get the report

Index / messaging

Chrome DevTools MCP

io-github-chromedevtools-chrome-devtools-mcp declares 32 capabilities across 32 tools, with 2 critical issues.

82/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package chrome-devtools-mcp@1.11.0 (published to npm as chrome-devtools-mcp, listed in the official MCP registry as io.github.ChromeDevTools/chrome-devtools-mcp 1.11.0), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 32 tools

32 of 32 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 32 tools

1 tool is classified as irreversible and declares no limit.

high · no-expiry · All 32 tools

32 of 32 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 32 tools

32 of 32 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 21 of 32 tools

21 tools can modify data and declare no limit.

low · uncapped-read · 10 of 32 tools

10 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
clickwrite assumed
close_pagedelete inferred
dragwrite assumed
emulatewrite assumed
evaluate_scriptwrite assumed
fillwrite assumed
fill_formwrite assumed
get_console_messageread declared
get_css_stylesread declared
get_network_requestread inferred
handle_dialogwrite assumed
hoverwrite assumed
lighthouse_auditread inferred
list_console_messagesread declared
list_network_requestsread declared
list_pagesread declared
navigate_pagewrite assumed
new_pagewrite assumed
performance_analyze_insightread declared
performance_start_tracewrite assumed
performance_stop_tracewrite assumed
press_keywrite assumed
resize_pagewrite assumed
screencast_startwrite assumed
screencast_stopwrite assumed
select_pageread declared
take_heapsnapshotwrite assumed
take_screenshotwrite assumed
take_snapshotwrite assumed
type_textwrite assumed
upload_filewrite inferred
wait_forread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-1279 tools/list answered by the npm package chrome-devtools-mcp@1.10.1 (published to npm as chrome-devtools-mcp, listed in the official MCP registry as io.github.ChromeDevTools/chrome-devtools-mcp 1.10.1), run in an isolated container with no network access and no credentials
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.