Permanently delete a SoundCloud playlist.
AI agents call delete_playlist to permanently remove resources in Soundcloud — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes user data (a playlist) that cannot be recovered or undone. It meets the definition of Destructive category. Severity is high because deletion of user-created content represents significant data loss, though the blast radius is limited to a single playlist rather than wholesale account destruction (which would be critical).
From the tool's definition Tool name is 'delete_playlist' and description states 'Permanently delete a SoundCloud playlist.' The word 'Permanently' explicitly indicates irreversible deletion.
Attacks that exploit this kind of access
Permanently delete a SoundCloud playlist. It is categorised as a Destructive tool in the Soundcloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Soundcloud 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 Soundcloud. 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 Soundcloud MCP server (marcellkehmstedt/soundcloud-mcp-server). 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 →