video_trim
Trims a video to one or more time ranges (milliseconds), concatenated in order into a NEW file — e.g. keep [{start_ms:0,end_ms:6000},{start_ms:126000,end_ms:223000}] to drop a dead segment. Audio is carried along. Returns the output path + duration. Never overwrites the input in place.
This record as markdown: /tools/com-local-mcp-local-mcp/video-trim.md
What video_trim does on Local
AI agents use video_trim to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | Yes | Path to the source video. |
output | string | — | Output path (default: <input>_trimmed.mov). |
ranges | array | Yes | Ordered [{start_ms, end_ms}] to keep. |
Parameters from the server's own tool schema.
Why video_trim is rated Medium
This tool creates a new video file by trimming and concatenating segments from an input video. It explicitly states it never overwrites the original, making it a reversible write operation (new file creation). The original file remains intact, so it is not Destructive. Severity is medium because it writes new files to the filesystem, which could be misused to fill disk space or create unauthorized copies of media.
From the tool's definition Trims a video to one or more time ranges...concatenated in order into a NEW file — Never overwrites the input in place. Returns the output path + duration.
Attacks that exploit this kind of access
The rule that runs video_trim safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For video_trim, this is the rule to start with:
video_trim 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 Local, apply this rule, and every video_trim call is checked against it from then on.
Questions about video_trim
Trims a video to one or more time ranges (milliseconds), concatenated in order into a NEW file — e.g. keep [{start_ms:0,end_ms:6000},{start_ms:126000,end_ms:223000}] to drop a dead segment. Audio is carried along. Returns the output path + duration. Never overwrites the input in place. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
video_trim accepts 3 parameters: input, output, ranges. Required: input, ranges. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for video_trim: 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 Local. Nothing to install.
video_trim 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 video_trim 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 video_trim. 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.
video_trim is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue