restore_project_snapshot
Restore a snapshot while automatically preserving the current state as a safety snapshot.
This record as markdown: /tools/cutpilot/restore-project-snapshot.md
What restore_project_snapshot does on Cutpilot
AI agents use restore_project_snapshot to create or update resources in Cutpilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cutpilot environment.
Why restore_project_snapshot is rated Medium
An AI agent can call restore_project_snapshot faster than any human can review: one bad instruction and it creates or modifies resources in Cutpilot by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs restore_project_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restore_project_snapshot, this is the rule to start with:
restore_project_snapshot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cutpilot, apply this rule, and every restore_project_snapshot call is checked against it from then on.
Questions about restore_project_snapshot
Restore a snapshot while automatically preserving the current state as a safety snapshot. It is categorised as a Write tool in the Cutpilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cutpilot MCP server in PolicyLayer and add a rule for restore_project_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 Cutpilot. Nothing to install.
restore_project_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_project_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.
Set action: deny in the PolicyLayer policy for restore_project_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.
restore_project_snapshot is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
This server
Across the catalogue