Delete a video generation job and its associated data.
AI agents call delete_video to permanently remove resources in Sora 2 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes video data and generation jobs. Once deleted, the data cannot be recovered. This is a classic destructive action (delete operation) that has a high blast radius if an AI agent mistakenly or maliciously deletes videos the user intended to keep. The fact that it removes 'associated data' compounds the severity of data loss.
From the tool's definition Tool name 'delete_video' and description states it will 'Delete a video generation job and its associated data' — this is an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete a video generation job and its associated data. It is categorised as a Destructive tool in the Sora 2 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sora 2 MCP Server MCP server in PolicyLayer and add a rule for delete_video: 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 Sora 2 MCP Server. Nothing to install.
delete_video 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_video 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_video. 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_video is provided by the Sora 2 MCP Server MCP server (writingmate/sora-2-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 →