clean_transcript
Mechanically remove fixed fillers and compress long gaps in timestamped cues.
This record as markdown: /tools/cutpilot/clean-transcript.md
What clean_transcript does on Cutpilot
AI agents use clean_transcript 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 clean_transcript is rated Medium
The tool modifies existing transcript data by removing filler words and compressing gaps. This is a reversible write operation (the original could be preserved), but it does alter/overwrite the timestamped cues. It does not execute code, delete assets irreversibly, or involve financial transactions. Severity is medium because misuse could corrupt transcript timing data used downstream in video editing workflows.
From the tool's definition "Mechanically remove fixed fillers and compress long gaps in timestamped cues"
Attacks that exploit this kind of access
The rule that runs clean_transcript 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 clean_transcript, this is the rule to start with:
clean_transcript 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 clean_transcript call is checked against it from then on.
Questions about clean_transcript
Mechanically remove fixed fillers and compress long gaps in timestamped cues. 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 clean_transcript: 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.
clean_transcript 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 clean_transcript 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 clean_transcript. 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.
clean_transcript 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