memory_integrity_check
Check executable memory regions against their corresponding on-disk PE files (.text sections) to detect modifications like inline hooks or code patches.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/memory-integrity-check.md
What memory_integrity_check does on Jshookmcp
AI agents call memory_integrity_check 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.
Why memory_integrity_check is rated Low
Performs memory forensics comparison only; does not modify, execute, or delete data.
From the tool's definition Check executable memory regions against on-disk PE files for modifications
Attacks that exploit this kind of access
The rule that runs memory_integrity_check 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_integrity_check, this is the rule to start with:
memory_integrity_check 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 Jshookmcp, apply this rule, and every memory_integrity_check call is checked against it from then on.
Questions about memory_integrity_check
Check executable memory regions against their corresponding on-disk PE files (.text sections) to detect modifications like inline hooks or code patches. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for memory_integrity_check: 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.
memory_integrity_check 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 memory_integrity_check 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 memory_integrity_check. 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.
memory_integrity_check 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.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue