export_video
Render the final MP4 (Remotion). Fetches the current timeline and queues the render. Async — poll get_workflow_status for the video_export job, then call get_video_url.
This record as markdown: /tools/com-framesail-framesail/export-video.md
What export_video does on Framesail
AI agents invoke export_video to trigger actions in Framesail. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
Parameters from the server's own tool schema.
Why export_video is rated High
This tool triggers an external rendering operation (Remotion engine) that processes the full timeline and produces a video file. It initiates a potentially long-running, resource-intensive job with real side effects (rendering pipeline, storage of output). This fits Execute as it runs an external process whose output depends on the current project state.
From the tool's definition 'Render the final MP4 (Remotion). Fetches the current timeline and queues the render.'
Attacks that exploit this kind of access
The rule that runs export_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For export_video, this is the rule to start with:
export_video stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every export_video call is checked against it from then on.
Questions about export_video
Render the final MP4 (Remotion). Fetches the current timeline and queues the render. Async — poll get_workflow_status for the video_export job, then call get_video_url. It is categorised as a Execute tool in the Framesail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
export_video accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for export_video: 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 Framesail. Nothing to install.
export_video is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the export_video 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 export_video. 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.
export_video is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
Across the catalogue