fw_delete_playlist

Permanently delete an entire playlist. Requires confirm:true and is irreversible — get explicit user confirmation in the conversation before calling.

SERVERCrow SOURCEkh0pper/crow
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/fw-delete-playlist.md

What fw_delete_playlist does on Crow

AI agents call fw_delete_playlist to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why fw_delete_playlist is rated Critical

This tool irreversibly deletes data (a playlist) with no recovery option. While the blast radius is limited to a single playlist rather than critical infrastructure, the permanent and irreversible nature of the deletion places it in the Destructive category at high severity.

From the tool's definition The description explicitly states 'Permanently delete an entire playlist' and 'is irreversible' with a requirement for explicit user confirmation, indicating data loss that cannot be undone.

Risk signalsBulk/mass operation — affects multiple targets

Questions about fw_delete_playlist

What does the fw_delete_playlist tool do? +

Permanently delete an entire playlist. Requires confirm:true and is irreversible — get explicit user confirmation in the conversation before calling. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on fw_delete_playlist? +

Register the Crow MCP server in PolicyLayer and add a rule for fw_delete_playlist: 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 Crow. Nothing to install.

What risk level is fw_delete_playlist? +

fw_delete_playlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit fw_delete_playlist? +

Yes. Add a rate_limit block to the fw_delete_playlist 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.

How do I block fw_delete_playlist completely? +

Set action: deny in the PolicyLayer policy for fw_delete_playlist. 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.

What MCP server provides fw_delete_playlist? +

fw_delete_playlist is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Crow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.