get_heapsnapshot_details
Loads a memory heapsnapshot and returns all available information including statistics, static data, and aggregated node information. Supports pagination for aggregates.
This record as markdown: /tools/async23-chrome-devtools-mcp/get-heapsnapshot-details.md
What get_heapsnapshot_details does on Chrome Devtools
AI agents call get_heapsnapshot_details 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 get_heapsnapshot_details is rated Low
This tool reads heap snapshot data for debugging and analysis purposes. While it accesses memory details that could reveal sensitive information in the Chrome runtime context (medium severity due to potential information disclosure), it performs no writes, execution, deletion, or financial operations.
From the tool's definition Tool 'loads a memory heapsnapshot and returns all available information' - purely retrieves and queries existing heap snapshot data without modification or execution. Uses 'get' verb and 'returns' language indicating read-only retrieval.
Attacks that exploit this kind of access
The rule that runs get_heapsnapshot_details 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 get_heapsnapshot_details, this is the rule to start with:
get_heapsnapshot_details 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 get_heapsnapshot_details call is checked against it from then on.
Questions about get_heapsnapshot_details
Loads a memory heapsnapshot and returns all available information including statistics, static data, and aggregated node information. Supports pagination for aggregates. 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 get_heapsnapshot_details: 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.
get_heapsnapshot_details 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 get_heapsnapshot_details 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 get_heapsnapshot_details. 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.
get_heapsnapshot_details 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