activate_timeline
Switch the active sequence used by editing, preview, validation, and rendering tools.
This record as markdown: /tools/cutpilot/activate-timeline.md
What activate_timeline does on Cutpilot
AI agents invoke activate_timeline 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 activate_timeline is rated High
This tool changes the active state of the application by switching which sequence/timeline is currently active. It triggers a state change that affects downstream operations (editing, preview, validation, rendering), making it an Execute-level action rather than a simple Read or Write. Misuse could redirect all subsequent editing and rendering operations to an unintended timeline, with medium blast radius.
From the tool's definition Switch the active sequence used by editing, preview, validation, and rendering tools
Attacks that exploit this kind of access
The rule that runs activate_timeline 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 activate_timeline, this is the rule to start with:
activate_timeline 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 activate_timeline call is checked against it from then on.
Questions about activate_timeline
Switch the active sequence used by editing, preview, validation, and rendering tools. 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 activate_timeline: 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.
activate_timeline 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 activate_timeline 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 activate_timeline. 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.
activate_timeline 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