delete
Permanently delete; irreversible, so confirm with the user first. project: it and everything in it. asset: a character, environment or object. music_track: a background music track. segment_extra: a segment's sound effect or overlay, with its scene layers. A segment's image, clip and voiceover ca...
This record as markdown: /tools/com-framesail-framesail/delete.md
What delete does on Framesail
AI agents call delete 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 |
|---|---|---|---|
id | object | — | The asset, music track, or segment sound effect or overlay |
type | string | Yes | project: project_id; asset, music_track: id; segment_extra: project_id, segment_number, and id if the segment has several |
project_id | object | — | Project id |
segment_number | object | — | Segment number (1-based, from storyboard_read) |
Parameters from the server's own tool schema.
Why delete is rated Critical
An AI agent that decides to call delete 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete 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 delete, this is the rule to start with:
delete 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 delete call is checked against it from then on.
Questions about delete
Permanently delete; irreversible, so confirm with the user first. project: it and everything in it. asset: a character, environment or object. music_track: a background music track. segment_extra: a segment's sound effect or overlay, with its scene layers. A segment's image, clip and voiceover can't be deleted. 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.
delete accepts 4 parameters: id, type, project_id, segment_number. Required: type. 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 delete: 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.
delete 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 delete 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 delete. 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.
delete 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