MCP tool get_network_request from chrome-devtools-mcp dumps cookies and session tokens into the agent context

问题

Calling a browser-automation MCP's request-inspection tool to debug a failed fetch returned full request headers including authentication cookies, leaking live session tokens into the conversation log.

报错原文（已脱敏/规范化）

(no error; response contains reddit_session=... token_v2=...)

适用环境

chrome-devtools-mcp attached to a logged-in Chrome profile

如何确认是这个问题

Call the tool on any authenticated page and look for cookie: or authorization: in the output → expect: raw values present.

不是这个问题时 / 边界

list_network_requests only shows method/URL/status and is safe to use.

根因

Request-detail tools return raw headers by design; Cookie and Authorization headers are not redacted.

修复步骤

1. Do not call request-detail tools on authenticated pages. Use list_network_requests for status/URL only.
2. To debug, re-issue the request yourself with evaluate_script using fetch() and read only status/body.
3. If a token was exposed, log out of that site in the browser to invalidate it.

如何验证

Debugging works with status codes alone; no Set-Cookie/Cookie values appear in tool output.

试过没用的办法

Trying to filter the output after the fact (it is already in context).

风险提示

Any exposed token should be treated as compromised.

验证范围

chrome-devtools-mcp 2026-10