delete_playlist

Delete an existing playlist from Music.

SERVERIconnect SOURCEiconnect-mcp
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/io-github-heznpc-iconnect/delete-playlist.md

What delete_playlist does on Iconnect

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

Why delete_playlist is rated Critical

Deletion of playlists cannot be undone and represents permanent data loss. While the blast radius is limited to music playlists (not system-critical), the irreversible nature of deletion places this in the Destructive category rather than Write. Severity is high because an AI agent could delete user-curated playlists, causing data loss, though financial or system-wide impact is unlikely.

From the tool's definition Tool name 'delete_playlist' combined with description 'Delete an existing playlist from Music' explicitly performs deletion, which is irreversible.

Questions about delete_playlist

What does the delete_playlist tool do? +

Delete an existing playlist from Music. It is categorised as a Destructive tool in the Iconnect 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 delete_playlist? +

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

What risk level is delete_playlist? +

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 delete_playlist? +

Yes. Add a rate_limit block to the 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 delete_playlist completely? +

Set action: deny in the PolicyLayer policy for 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 delete_playlist? +

delete_playlist is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Iconnect, 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 Iconnect'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.