Loads a memory heapsnapshot and returns retaining paths for a specific node ID. This helps to understand why a node is not being garbage collected.
AI agents call get_heapsnapshot_retaining_paths 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.
The tool reads and analyzes an existing heap snapshot to retrieve retaining path information. It performs no writes, executions, or destructive operations — purely querying/inspecting memory snapshot data.
From the tool's definition Loads a memory heapsnapshot and returns retaining paths for a specific node ID. This helps to understand why a node is not being garbage collected.
Documented attack patterns abuse exactly the kind of access get_heapsnapshot_retaining_paths gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome DevTools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_heapsnapshot_retaining_paths:
{
"version": "1",
"default": "deny",
"tools": {
"get_heapsnapshot_retaining_paths": {}
}
}get_heapsnapshot_retaining_paths is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Loads a memory heapsnapshot and returns retaining paths for a specific node ID. This helps to understand why a node is not being garbage collected. 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_retaining_paths: 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_retaining_paths 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_retaining_paths 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_retaining_paths. 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_retaining_paths is provided by the Chrome DevTools MCP server (ChromeDevTools/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome DevTools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Chrome DevTools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.