get_heapsnapshot_dominators

Loads a memory heapsnapshot and returns the dominator chain for a specific node ID. This helps to identify which objects are keeping the target node alive.

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/get-heapsnapshot-dominators.md

WHAT IT DOES

What get_heapsnapshot_dominators does on Chrome Devtools

AI agents call get_heapsnapshot_dominators 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.

RISK

Why get_heapsnapshot_dominators is rated Low

Tool retrieves and analyzes existing memory snapshot data without modifying browser state or executing code.

From the tool's definition Loads memory heapsnapshot, returns dominator chain, identifies objects keeping node alive.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_heapsnapshot_dominators 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_dominators, this is the rule to start with:

get_heapsnapshot_dominators Allowed

get_heapsnapshot_dominators is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_heapsnapshot_dominators": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every get_heapsnapshot_dominators call is checked against it from then on.

FAQ

Questions about get_heapsnapshot_dominators

What does the get_heapsnapshot_dominators tool do? +

Loads a memory heapsnapshot and returns the dominator chain for a specific node ID. This helps to identify which objects are keeping the target node alive. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_heapsnapshot_dominators? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_heapsnapshot_dominators: 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.

What risk level is get_heapsnapshot_dominators? +

get_heapsnapshot_dominators is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_heapsnapshot_dominators? +

Yes. Add a rate_limit block to the get_heapsnapshot_dominators 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.

How do I block get_heapsnapshot_dominators completely? +

Set action: deny in the PolicyLayer policy for get_heapsnapshot_dominators. 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.

What MCP server provides get_heapsnapshot_dominators? +

get_heapsnapshot_dominators 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.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →