get_heapsnapshot_edges
Loads a memory heapsnapshot and returns outgoing edges (references) for a specific node ID.
This record as markdown: /tools/async23-chrome-devtools-mcp/get-heapsnapshot-edges.md
What get_heapsnapshot_edges does on Chrome Devtools
AI agents call get_heapsnapshot_edges 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_edges is rated Low
This tool queries and retrieves memory snapshot data for analysis purposes. It reads existing heap snapshot information and returns references without creating, modifying, deleting, or executing code. The operation is read-only and non-destructive, making it a Read category tool with low severity since heap analysis cannot directly harm system state or external data.
From the tool's definition Tool description states it 'Loads a memory heapsnapshot and returns outgoing edges' — a retrieval operation with no modification or deletion. The verb 'returns' indicates data querying only.
Attacks that exploit this kind of access
The rule that runs get_heapsnapshot_edges 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_edges, this is the rule to start with:
get_heapsnapshot_edges 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_edges call is checked against it from then on.
Questions about get_heapsnapshot_edges
Loads a memory heapsnapshot and returns outgoing edges (references) for a specific node ID. 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_edges: 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_edges 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_edges 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_edges. 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_edges 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