New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

coordination_restore_snapshot

Restore a saved page snapshot including IndexedDB data. Navigates to the captured URL, re-injects cookies, localStorage, sessionStorage, and IndexedDB records from the snapshot.

SERVERJshookmcp SOURCE@jshookmcp/jshook
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/coordination-restore-snapshot.md

What coordination_restore_snapshot does on Jshookmcp

AI agents use coordination_restore_snapshot to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.

Why coordination_restore_snapshot is rated Medium

Modifies browser state by restoring multiple data stores, reversibly altering client-side persistence without destructive deletion.

From the tool's definition Restore snapshot, re-inject cookies, localStorage, sessionStorage, IndexedDB records

Questions about coordination_restore_snapshot

What does the coordination_restore_snapshot tool do? +

Restore a saved page snapshot including IndexedDB data. Navigates to the captured URL, re-injects cookies, localStorage, sessionStorage, and IndexedDB records from the snapshot. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on coordination_restore_snapshot? +

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

coordination_restore_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit coordination_restore_snapshot? +

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

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

coordination_restore_snapshot 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Jshook's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.