memory_group_scan

Search for multiple values at known offsets simultaneously.

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-group-scan.md

WHAT IT DOES

What memory_group_scan does on Jshookmcp

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

Reads memory at specified offsets; no modification, but accesses potentially sensitive memory.

From the tool's definition Search for multiple values at known offsets simultaneously

Attacks that exploit this kind of access

RECOMMENDED RULE

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

memory_group_scan Allowed

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

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

FAQ

Questions about memory_group_scan

What does the memory_group_scan tool do? +

Search for multiple values at known offsets simultaneously. 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_group_scan? +

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

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

Can I rate-limit memory_group_scan? +

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

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

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