memory_read_typed
Read process memory as typed numeric values with explicit endianness. Decodes consecutive values starting at address via koffi endian-sensitive integer types (uint64_le / int32_be / …) — no manual byte swapping needed. 64-bit values are returned as decimal strings alongside two
This record as markdown: /tools/io-github-vmoranv-jshookmcp/memory-read-typed.md
What memory_read_typed does on Jshookmcp
AI agents call memory_read_typed 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_read_typed is rated Low
Retrieves sensitive process memory data without modification; high severity due to exposure of runtime secrets and state.
From the tool's definition Read process memory as typed numeric values with explicit endianness
Attacks that exploit this kind of access
The rule that runs memory_read_typed 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_read_typed, this is the rule to start with:
memory_read_typed 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_read_typed call is checked against it from then on.
Questions about memory_read_typed
Read process memory as typed numeric values with explicit endianness. Decodes consecutive values starting at address via koffi endian-sensitive integer types (uint64_le / int32_be / …) — no manual byte swapping needed. 64-bit values are returned as decimal strings alongside two. 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_read_typed: 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_read_typed 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_read_typed 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_read_typed. 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_read_typed 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