This record as markdown: /tools/cutpilot/trim-item.md
What trim_item does on Cutpilot
AI agents use trim_item 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 trim_item is rated Medium
Trimming a video/audio item cuts its duration by adjusting in/out points, which modifies the project state reversibly. This is a Write operation (modifies data) rather than Destructive (since the original source asset remains unchanged, and the edit can be undone). Severity is medium because misuse could corrupt editing work, but the operation is localized to a single item and the damage is recoverable.
From the tool's definition Tool name 'trim_item' and description 'Trim an item' indicate modification of video/media assets. Trimming is a reversible edit operation that modifies but does not delete data.
Attacks that exploit this kind of access
The rule that runs trim_item 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 trim_item, this is the rule to start with:
trim_item 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 trim_item call is checked against it from then on.
Questions about trim_item
Trim an item. 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 trim_item: 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.
trim_item 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 trim_item 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 trim_item. 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.
trim_item 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