fw_remove_from_playlist
Remove a single track from a playlist by its 0-based position (use fw_get_playlist_tracks to find the right index first). Funkwhale uses POST /remove/ with body {index} — not DELETE.
This record as markdown: /tools/kh0pper-crow/fw-remove-from-playlist.md
What fw_remove_from_playlist does on Crow
AI agents call fw_remove_from_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_remove_from_playlist is rated Critical
Removing a track from a playlist is a destructive operation — the track is deleted from the playlist and this action is not trivially reversible without knowing the original index and re-adding it. The description clarifies it uses POST /remove/ which modifies persistent playlist data irreversibly from the playlist's perspective.
From the tool's definition Remove a single track from a playlist by its 0-based position
Attacks that exploit this kind of access
The rule that runs fw_remove_from_playlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fw_remove_from_playlist, this is the rule to start with:
fw_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 Crow, apply this rule, and every fw_remove_from_playlist call is checked against it from then on.
Questions about fw_remove_from_playlist
Remove a single track from a playlist by its 0-based position (use fw_get_playlist_tracks to find the right index first). Funkwhale uses POST /remove/ with body {index} — not DELETE. 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.
Register the Crow MCP server in PolicyLayer and add a rule for fw_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 Crow. Nothing to install.
fw_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 fw_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 fw_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.
fw_remove_from_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.
Across the catalogue