get_heapsnapshot_summary
Loads a memory heapsnapshot and returns snapshot summary stats.
This record as markdown: /tools/async23-chrome-devtools-mcp/get-heapsnapshot-summary.md
What get_heapsnapshot_summary does on Chrome Devtools
AI agents call get_heapsnapshot_summary 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_summary is rated Low
This tool retrieves and queries memory diagnostic data from Chrome DevTools without side effects. It does not create, modify, delete, or execute code—it only provides introspection into the heap state. The blast radius of misuse is minimal: an attacker could learn about application memory layout or presence of sensitive objects in memory, but cannot directly compromise systems or trigger harmful actions.
From the tool's definition Tool name 'get_heapsnapshot_summary' and description 'Loads a memory heapsnapshot and returns snapshot summary stats' indicate a read-only diagnostic operation.
Attacks that exploit this kind of access
The rule that runs get_heapsnapshot_summary 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_summary, this is the rule to start with:
get_heapsnapshot_summary 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_summary call is checked against it from then on.
Questions about get_heapsnapshot_summary
Loads a memory heapsnapshot and returns snapshot summary stats. 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_summary: 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_summary 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_summary 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_summary. 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_summary 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