Loads a memory heapsnapshot and returns retainers for a specific node ID.
AI agents call get_heapsnapshot_retainers 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.
This tool retrieves and queries memory diagnostic information from a Chrome browser heapsnapshot without creating, modifying, or deleting any data. It is a read-only inspection capability used for debugging and performance analysis, with minimal blast radius if misused (information disclosure only).
From the tool's definition Tool name includes 'get_' prefix and description states it 'loads' and 'returns' data (heapsnapshot retainers). No modification, deletion, or execution of external operations occurs—purely data retrieval from an already-captured memory snapshot.
Attacks that exploit this kind of access
Loads a memory heapsnapshot and returns retainers 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_retainers: 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_retainers 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_retainers 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_retainers. 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_retainers is provided by the Chrome Devtools MCP server (zhang77-x/chrpme_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →