memory_scan_session

Manage scan sessions. Actions: list (all sessions), delete (by sessionId), export (as JSON).

SERVERJshookmcp SOURCE@jshookmcp/jshook

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/memory-scan-session.md

WHAT IT DOES

What memory_scan_session does on Jshookmcp

AI agents call memory_scan_session to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why memory_scan_session is rated Critical

Tool supports irreversible deletion of scan sessions by ID.

From the tool's definition delete (by sessionId), export (as JSON)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

memory_scan_session Hidden

memory_scan_session is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "memory_scan_session"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about memory_scan_session

What does the memory_scan_session tool do? +

Manage scan sessions. Actions: list (all sessions), delete (by sessionId), export (as JSON). It is categorised as a Destructive tool in the Jshookmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on memory_scan_session? +

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

memory_scan_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit memory_scan_session? +

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

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

memory_scan_session 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 → Critical-risk tools on this server →

Across the catalogue

clear_scan on Frida Game Hacking MCP →kill_ftp_session on cPanel MCP Server →clear-session on CodeAnalysis MCP Server →delete_memory on Cognio → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →