cutpilot_apply_plan
High-level reviewed apply: execute an explicitly approved built-in AI director or revision plan as one snapshot-protected edit.
This record as markdown: /tools/cutpilot/cutpilot-apply-plan.md
What cutpilot_apply_plan does on Cutpilot
AI agents invoke cutpilot_apply_plan to trigger actions in Cutpilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why cutpilot_apply_plan is rated High
This tool executes a pre-approved editing plan against a video project. While 'snapshot-protected' implies some reversibility, the core action is executing/applying an AI-generated edit plan that modifies the project. The execution of arbitrary editing operations (cuts, transitions, restructuring) driven by an AI plan makes this Execute category.
From the tool's definition "execute an explicitly approved built-in AI director or revision plan as one snapshot-protected edit"
Attacks that exploit this kind of access
The rule that runs cutpilot_apply_plan 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 cutpilot_apply_plan, this is the rule to start with:
cutpilot_apply_plan stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 cutpilot_apply_plan call is checked against it from then on.
Questions about cutpilot_apply_plan
High-level reviewed apply: execute an explicitly approved built-in AI director or revision plan as one snapshot-protected edit. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cutpilot MCP server in PolicyLayer and add a rule for cutpilot_apply_plan: 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.
cutpilot_apply_plan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cutpilot_apply_plan 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 cutpilot_apply_plan. 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.
cutpilot_apply_plan 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