undo_project
Undo the most recent saved project edit and make it available for redo.
This record as markdown: /tools/cutpilot/undo-project.md
What undo_project does on Cutpilot
AI agents use undo_project 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 undo_project is rated Medium
The undo operation modifies the project by reverting it to a previous state, which is characteristic of Write operations. It is not Read (no data retrieval), not Execute (no code/shell execution), not Destructive (changes are reversible via redo), not Financial, and not Other. Severity is medium because misuse could corrupt project work, but the reversible nature and local-first scope limit blast radius.
From the tool's definition Tool name 'undo_project' and description 'Undo the most recent saved project edit and make it available for redo' indicates reversal of edits within a video editing project. This is a write-class operation because it modifies project state reversibly.
Attacks that exploit this kind of access
The rule that runs undo_project 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 undo_project, this is the rule to start with:
undo_project 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 undo_project call is checked against it from then on.
Questions about undo_project
Undo the most recent saved project edit and make it available for redo. 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 undo_project: 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.
undo_project 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 undo_project 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 undo_project. 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.
undo_project 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