Delete one or more videos from your VideoSeek library by their video numbers.
AI agents call delete_videos to permanently remove resources in Videoseek — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of media files cannot be undone and results in permanent loss of data. This is a destructive action that matches the definition of the Destructive category (irreversibly deletes or overwrites data, or actions that cannot be undone).
From the tool's definition Tool name is 'delete_videos' and description states it will 'Delete one or more videos from your VideoSeek library by their video numbers' - this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete one or more videos from your VideoSeek library by their video numbers. It is categorised as a Destructive tool in the Videoseek MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Videoseek MCP server in PolicyLayer and add a rule for delete_videos: 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 Videoseek. Nothing to install.
delete_videos 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_videos 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_videos. 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_videos is provided by the Videoseek MCP server (kennyzheng-builds/videoseek-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 →