Capture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks.
AI agents call take_heapsnapshot to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A heap snapshot is a diagnostic read-only operation that captures runtime memory state for analysis purposes. It does not modify data, execute arbitrary scripts beyond introspection, delete resources, or perform financial operations.
From the tool's definition The tool 'take_heapsnapshot' captures a heap snapshot for analysis of memory distribution. The description explicitly states it is used to 'analyze' memory distribution and 'debug' memory leaks.
Attacks that exploit this kind of access
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 (zhang77-x/chrpme_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →