libi.delete_scene
Remove a scene FROM THE TIMELINE (composition manifest only). The source file is NOT deleted — it stays in resources, and the scene can be recreated. Any linked audio clip for this scene is also removed (the audio was bound to the scene); the response surfaces those cascaded clip ids in
This record as markdown: /tools/libi/libi.delete-scene.md
What libi.delete_scene does on Libi
AI agents call libi.delete_scene to permanently remove resources in Libi, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why libi.delete_scene is rated Critical
Irreversibly removes scene and linked audio from timeline; source file preserved but timeline edit is destructive.
From the tool's definition Remove a scene FROM THE TIMELINE... Any linked audio clip also removed
Attacks that exploit this kind of access
The rule that runs libi.delete_scene safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Libi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For libi.delete_scene, this is the rule to start with:
libi.delete_scene 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 Libi, apply this rule, and every libi.delete_scene call is checked against it from then on.
Questions about libi.delete_scene
Remove a scene FROM THE TIMELINE (composition manifest only). The source file is NOT deleted — it stays in resources, and the scene can be recreated. Any linked audio clip for this scene is also removed (the audio was bound to the scene); the response surfaces those cascaded clip ids in. It is categorised as a Destructive tool in the Libi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Libi MCP server in PolicyLayer and add a rule for libi.delete_scene: 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 Libi. Nothing to install.
libi.delete_scene 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 libi.delete_scene 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 libi.delete_scene. 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.
libi.delete_scene is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Libi, and thousands of servers like it.
Across the catalogue