take_heapsnapshot
Capture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks.
This record as markdown: /tools/async23-chrome-devtools-mcp/take-heapsnapshot.md
What take_heapsnapshot does on Chrome Devtools
AI agents call take_heapsnapshot 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 take_heapsnapshot is rated Low
While heap snapshots expose sensitive information about a page's runtime state (object graphs, memory contents, variable values), the operation is fundamentally a read/query action—it retrieves diagnostic data without modifying or destroying data, executing arbitrary code, or triggering external operations.
From the tool's definition Tool captures a heap snapshot—"Capture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks." Heap snapshots are read-only diagnostic data extractions that do not modify page state…
Attacks that exploit this kind of access
The rule that runs take_heapsnapshot 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 take_heapsnapshot, this is the rule to start with:
take_heapsnapshot 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 take_heapsnapshot call is checked against it from then on.
Questions about take_heapsnapshot
Capture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks. 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 take_heapsnapshot: 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.
take_heapsnapshot 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 take_heapsnapshot 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 take_heapsnapshot. 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.
take_heapsnapshot is provided by the Chrome Devtools MCP server (@async23/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