video_export_gif
Exports a video (or a [start_ms,end_ms] slice of it) to an optimized looping GIF — for README/social. fps (default 12) and width (default 640, height auto) control size. Returns the output path, frame count, and size.
This record as markdown: /tools/com-local-mcp-local-mcp/video-export-gif.md
What video_export_gif does on Local
AI agents use video_export_gif 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 |
|---|---|---|---|
fps | integer | — | Frames per second in the GIF (default 12). |
input | string | Yes | Path to the source video. |
width | integer | — | Output width in px, height scales to keep aspect (default 640). |
end_ms | integer | — | Slice end (default: end of video). |
output | string | — | Output path (default: <input>.gif). |
start_ms | integer | — | Slice start (default 0). |
Parameters from the server's own tool schema.
Why video_export_gif is rated Medium
The tool creates a new file artifact (GIF) on the file system from existing video data. This is a Write operation because it produces a new, persistent output file that didn't exist before. Severity is medium because while the operation is reversible (the GIF can be deleted) and has limited scope, exporting media files could inadvertently expose sensitive video content or create unwanted artifacts.
From the tool's definition Tool creates and exports new media file (GIF) from video source; description states 'Exports a video...to an optimized looping GIF' and 'Returns the output path', indicating file creation/modification with side effects.
Attacks that exploit this kind of access
The rule that runs video_export_gif 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_export_gif, this is the rule to start with:
video_export_gif 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_export_gif call is checked against it from then on.
Questions about video_export_gif
Exports a video (or a [start_ms,end_ms] slice of it) to an optimized looping GIF — for README/social. fps (default 12) and width (default 640, height auto) control size. Returns the output path, frame count, and size. 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_export_gif accepts 6 parameters: fps, input, width, end_ms, output, start_ms. Required: input. 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_export_gif: 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_export_gif 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_export_gif 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_export_gif. 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_export_gif 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