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.
Attacks that exploit this kind of access
The rule that runs delete_playlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_playlist, this is the rule to start with:
delete_playlist is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every delete_playlist call is checked against it from then on.
Questions about delete_playlist
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.
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.
delete_playlist 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_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.
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.
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.
Across the catalogue