snapshot_restore

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/snapshot-restore.md

WHAT IT DOES

What snapshot_restore does on Jshookmcp

AI agents call snapshot_restore 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 snapshot_restore is rated Critical

Irreversibly overwrites, deletes, and reverts files to a prior snapshot state.

From the tool's definition files modified after the snapshot are overwritten, files created after it are DELETED

Attacks that exploit this kind of access

RECOMMENDED RULE

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

snapshot_restore Hidden

snapshot_restore 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": [
    "snapshot_restore"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about snapshot_restore

What does the snapshot_restore tool do? +

Restore a directory to a recorded shadow-git snapshot. DESTRUCTIVE: files modified after the snapshot are overwritten, files created after it are DELETED, and files deleted after it are written back (full revert semantics). The isolated store never touches the project .git. Create a fresh snapshot_create first if you may need the current state. 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 snapshot_restore? +

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

snapshot_restore 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 snapshot_restore? +

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

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

snapshot_restore 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

delete_snapshot on Why Did You Render → All critical-risk MCP tools → The MCP Attack Database →

Guides

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