set_transition
Set fade, dip, dissolve, directional wipe, radial reveal, or directional slide transition on an item boundary.
This record as markdown: /tools/cutpilot/set-transition.md
What set_transition does on Cutpilot
AI agents use set_transition 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 set_transition is rated Medium
This tool modifies a timeline item by applying a transition effect between clips. It creates/updates a transition property on an item boundary, which is a reversible write operation within a video editing project. No data is deleted, no code is executed, and no financial transactions occur.
From the tool's definition Set fade, dip, dissolve, directional wipe, radial reveal, or directional slide transition on an item boundary.
Attacks that exploit this kind of access
The rule that runs set_transition 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 set_transition, this is the rule to start with:
set_transition 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 set_transition call is checked against it from then on.
Questions about set_transition
Set fade, dip, dissolve, directional wipe, radial reveal, or directional slide transition on an item boundary. 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 set_transition: 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.
set_transition 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 set_transition 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 set_transition. 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.
set_transition 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