This record as markdown: /tools/io-github-heznpc-iconnect/remove-from-playlist.md
What remove_from_playlist does on Iconnect
AI agents call remove_from_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 remove_from_playlist is rated Critical
Removing a track from a playlist is a destructive action that modifies the playlist by deleting an entry. Depending on the music application (e.g., Apple Music), this action may not be easily reversible, making it Destructive rather than just Write. The blast radius is medium since it affects playlist organization but not the underlying music library.
From the tool's definition 'Remove a track from a playlist' — removes content from a playlist, which may be irreversible depending on the application.
Attacks that exploit this kind of access
The rule that runs remove_from_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 remove_from_playlist, this is the rule to start with:
remove_from_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 remove_from_playlist call is checked against it from then on.
Questions about remove_from_playlist
Remove a track from a playlist. 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 remove_from_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.
remove_from_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 remove_from_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 remove_from_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.
remove_from_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