memory_parse_dump

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/memory-parse-dump.md

WHAT IT DOES

What memory_parse_dump does on Jshookmcp

AI agents call memory_parse_dump 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 memory_parse_dump is rated Low

Reads and parses a dump file for forensic analysis; no data modification occurs.

From the tool's definition Parse a Windows Minidump file and extract forensic information

Attacks that exploit this kind of access

RECOMMENDED RULE

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

memory_parse_dump Allowed

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

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 memory_parse_dump call is checked against it from then on.

FAQ

Questions about memory_parse_dump

What does the memory_parse_dump tool do? +

Parse a Windows Minidump (.dmp) file and extract forensic information: loaded modules (base/size/name/timestamp), threads (ID/stack/context), memory ranges (64-bit or 32-bit), system info (OS/CPU), and exception records. Optionally resolve a list of addresses against the dump contents. Pure TS — cross-platform (can analyze Windows dumps on Linux/macOS). 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 memory_parse_dump? +

Register the Jshook MCP server in PolicyLayer and add a rule for memory_parse_dump: 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 memory_parse_dump? +

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

Can I rate-limit memory_parse_dump? +

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

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

memory_parse_dump 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 →