plan_vlog_rhythm
Create a non-mutating Vlog rhythm-director plan with safe visual prelaps, cutaway handoffs, audio fades, voice anchoring, music ducking, and separately listed manual editorial decisions.
This record as markdown: /tools/cutpilot/plan-vlog-rhythm.md
What plan_vlog_rhythm does on Cutpilot
AI agents call plan_vlog_rhythm to retrieve information from Cutpilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why plan_vlog_rhythm is rated Low
The tool generates a planning/analysis artifact (a rhythm-director plan) without making any changes to the project, timeline, or assets. 'Non-mutating' confirms no side effects. This is equivalent to a read/query operation that returns structured recommendations.
From the tool's definition "Create a non-mutating Vlog rhythm-director plan" — explicitly states non-mutating; produces a plan only without modifying any timeline or asset
Attacks that exploit this kind of access
The rule that runs plan_vlog_rhythm 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 plan_vlog_rhythm, this is the rule to start with:
plan_vlog_rhythm is read-only, so it stays allowed. 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 plan_vlog_rhythm call is checked against it from then on.
Questions about plan_vlog_rhythm
Create a non-mutating Vlog rhythm-director plan with safe visual prelaps, cutaway handoffs, audio fades, voice anchoring, music ducking, and separately listed manual editorial decisions. It is categorised as a Read tool in the Cutpilot MCP Server, which means it retrieves data without modifying state.
Register the Cutpilot MCP server in PolicyLayer and add a rule for plan_vlog_rhythm: 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.
plan_vlog_rhythm is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plan_vlog_rhythm 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 plan_vlog_rhythm. 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.
plan_vlog_rhythm 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