build_scenes
Compile segments + assets + voiceover into the editor/render timeline (scenes). Run after segment assets are complete, before export.
This record as markdown: /tools/com-framesail-framesail/build-scenes.md
What build_scenes does on Framesail
AI agents invoke build_scenes 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 build_scenes is rated High
The tool executes a compilation operation that orchestrates multiple inputs (segments, assets, voiceover) into a structured output (render timeline/scenes). While not destructive or financial, it performs a procedural action whose outcome depends on argument configuration and prior state.
From the tool's definition Tool 'compiles segments + assets + voiceover into the editor/render timeline' and must be 'run after segment assets are complete'.
Attacks that exploit this kind of access
The rule that runs build_scenes 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 build_scenes, this is the rule to start with:
build_scenes 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 build_scenes call is checked against it from then on.
Questions about build_scenes
Compile segments + assets + voiceover into the editor/render timeline (scenes). Run after segment assets are complete, before export. 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.
build_scenes 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 build_scenes: 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.
build_scenes 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 build_scenes 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 build_scenes. 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.
build_scenes 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