director_note
Edit ONE scene with a natural-language note (the same director chat the editor UI uses): move/restyle/add/remove layers and overlays, retime, etc. Synchronous — returns the applied mutations + updated scene. Address the scene by project_id + segment_number (preferred — always resolves to the curr...
This record as markdown: /tools/com-framesail-framesail/director-note.md
What director_note does on Framesail
AI agents call director_note to permanently remove resources in Framesail, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Natural-language edit note for this scene, e.g. "move the caption to the top" or "remove the overlay" |
scene_id | object | — | ID of the scene to edit, from a FRESH list_scenes call — scene ids change whenever segments are edited (split/combine/update-content), so never reuse ids saved |
project_id | object | — | Project ID; required (with segment_number) when not passing scene_id |
segment_number | object | — | 1-based segment number of the scene to edit (from list_scenes or get_segments) — preferred over scene_id because it is resolved to the current scene at call tim |
conversation_history | object | — | Prior chat turns as [{"role": ..., "content": ...}] to continue an editing conversation on this scene; omit to start fresh |
Parameters from the server's own tool schema.
Why director_note is rated Critical
An AI agent that decides to call director_note doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Framesail is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs director_note 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 director_note, this is the rule to start with:
director_note is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every director_note call is checked against it from then on.
Questions about director_note
Edit ONE scene with a natural-language note (the same director chat the editor UI uses): move/restyle/add/remove layers and overlays, retime, etc. Synchronous — returns the applied mutations + updated scene. Address the scene by project_id + segment_number (preferred — always resolves to the current scene) or by scene_id from a fresh list_scenes call. Scene durations are locked to the narration track: don't ask to extend/shorten a scene except the final one — for a held-shot feel mid-video, ask for calmer/static motion on the scene instead. For notes spanning the whole video use project_director_note instead. It is categorised as a Destructive tool in the Framesail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
director_note accepts 5 parameters: message, scene_id, project_id, segment_number, conversation_history. Required: message. 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 director_note: 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.
director_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the director_note 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 director_note. 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.
director_note 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