delete_asset
Delete a project asset (e.g. one the scan over-extracted).
This record as markdown: /tools/com-framesail-framesail/delete-asset.md
What delete_asset does on Framesail
AI agents call delete_asset 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 |
|---|---|---|---|
asset_id | string | Yes | ID of the asset to delete, from list_assets |
Parameters from the server's own tool schema.
Why delete_asset is rated Critical
This tool performs irreversible data deletion. Once a project asset is deleted, it cannot be undone through the API. In the context of a video production system, deleted assets (scenes, audio, segments, or final renders) represent lost work. While the blast radius is limited to project assets rather than external systems, the destructive nature and irreversibility classify this as Destructive rather than Write.
From the tool's definition Tool name 'delete_asset' combined with description 'Delete a project asset' indicates irreversible deletion. The context of a video creation tool means assets include scripts, storyboards, voiceovers, or MP4 segments that cannot be recovered once deleted.
Attacks that exploit this kind of access
The rule that runs delete_asset 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_asset, this is the rule to start with:
delete_asset 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_asset call is checked against it from then on.
Questions about delete_asset
Delete a project asset (e.g. one the scan over-extracted). 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_asset accepts 1 parameter: asset_id. Required: asset_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 delete_asset: 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_asset 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_asset 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_asset. 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_asset 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