repair_cutpilot_project
Create a safety snapshot, migrate an old project schema, and remove structurally invalid references only after explicit approval.
This record as markdown: /tools/cutpilot/repair-cutpilot-project.md
What repair_cutpilot_project does on Cutpilot
AI agents call repair_cutpilot_project to permanently remove resources in Cutpilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why repair_cutpilot_project is rated Critical
An AI agent that decides to call repair_cutpilot_project doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Cutpilot is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs repair_cutpilot_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 repair_cutpilot_project, this is the rule to start with:
repair_cutpilot_project is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cutpilot, apply this rule, and every repair_cutpilot_project call is checked against it from then on.
Questions about repair_cutpilot_project
Create a safety snapshot, migrate an old project schema, and remove structurally invalid references only after explicit approval. It is categorised as a Destructive tool in the Cutpilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cutpilot MCP server in PolicyLayer and add a rule for repair_cutpilot_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.
repair_cutpilot_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the repair_cutpilot_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 repair_cutpilot_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.
repair_cutpilot_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.
Across the catalogue