Removes a clip from memory and closes it.
AI agents call delete_clip to permanently remove resources in vidMagik-mcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the deletion appears scoped to in-memory clips rather than permanent file deletion, the action is irreversible within an editing session and eliminates data that cannot be recovered without reloading the source. In the context of an AI agent autonomously managing video projects, accidental deletion of clips could compromise entire editing workflows.
From the tool's definition Tool name 'delete_clip' combined with description 'Removes a clip from memory and closes it' indicates irreversible deletion of video/audio data.
Attacks that exploit this kind of access
Removes a clip from memory and closes it. It is categorised as a Destructive tool in the vidMagik-mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the vidMagik- MCP server in PolicyLayer and add a rule for delete_clip: 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 vidMagik-mcp. Nothing to install.
delete_clip 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_clip 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_clip. 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_clip is provided by the vidMagik- MCP server (vizionik25/vidmagik-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →