diff_heap_snapshots

Compare two heap snapshots from a trace.

SERVERJshookmcp SOURCE@jshookmcp/jshook

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/io-github-vmoranv-jshookmcp/diff-heap-snapshots.md

WHAT IT DOES

What diff_heap_snapshots does on Jshookmcp

AI agents call diff_heap_snapshots to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why diff_heap_snapshots is rated Low

Tool compares existing snapshots for analysis only; read-only operation with no side effects.

From the tool's definition Compare two heap snapshots from a trace. No modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs diff_heap_snapshots safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For diff_heap_snapshots, this is the rule to start with:

diff_heap_snapshots Allowed

diff_heap_snapshots 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": {
    "diff_heap_snapshots": {}
  }
}

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

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

FAQ

Questions about diff_heap_snapshots

What does the diff_heap_snapshots tool do? +

Compare two heap snapshots from a trace. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diff_heap_snapshots? +

Register the Jshook MCP server in PolicyLayer and add a rule for diff_heap_snapshots: 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 Jshookmcp. Nothing to install.

What risk level is diff_heap_snapshots? +

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

Can I rate-limit diff_heap_snapshots? +

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

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

diff_heap_snapshots is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

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