Delete downloads from the queue or completed list.
AI agents call metube_delete_downloads to permanently remove resources in Metube — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes download records that cannot be undone. While the actual downloaded files may exist separately, deletion from the queue/completed list is a destructive action with no recovery mechanism. This is more severe than Write (reversible modification) and qualifies as Destructive.
From the tool's definition Tool name is 'metube_delete_downloads' and description states 'Delete downloads from the queue or completed list.' The verb 'Delete' combined with permanent removal from queue or completed list indicates irreversible destruction of data/records.
Attacks that exploit this kind of access
Delete downloads from the queue or completed list. It is categorised as a Destructive tool in the Metube MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Metube MCP server in PolicyLayer and add a rule for metube_delete_downloads: 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 Metube. Nothing to install.
metube_delete_downloads 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 metube_delete_downloads 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 metube_delete_downloads. 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.
metube_delete_downloads is provided by the Metube MCP server (junglem0nkey/metube-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 →