get_heapsnapshot_details

Loads a memory heapsnapshot and returns all available information including statistics, static data, and aggregated node information. Supports pagination for aggregates.

Server Chrome Devtools zhang77-x/chrpme_mcp
Category Read
Risk class Low
Parameters 00 required

What get_heapsnapshot_details does on Chrome Devtools

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

Why get_heapsnapshot_details needs a policy

This tool reads heap snapshot data for debugging and analysis purposes. While it accesses memory details that could reveal sensitive information in the Chrome runtime context (medium severity due to potential information disclosure), it performs no writes, execution, deletion, or financial operations.

From the tool's definition Tool 'loads a memory heapsnapshot and returns all available information' - purely retrieves and queries existing heap snapshot data without modification or execution. Uses 'get' verb and 'returns' language indicating read-only retrieval.

Questions about get_heapsnapshot_details

What does the get_heapsnapshot_details tool do? +

Loads a memory heapsnapshot and returns all available information including statistics, static data, and aggregated node information. Supports pagination for aggregates. 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_details? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_heapsnapshot_details: 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_details? +

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

Can I rate-limit get_heapsnapshot_details? +

Yes. Add a rate_limit block to the get_heapsnapshot_details 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_details completely? +

Set action: deny in the PolicyLayer policy for get_heapsnapshot_details. 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_details? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.