Append tracks to an existing playlist. track_ids are integer Funkwhale track IDs (from fw_search type=
AI agents use fw_add_to_playlist to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
The tool modifies a playlist by appending tracks to it. This is a Write operation because it changes data in a reversible manner (tracks can be removed). It has low severity because misuse would only affect the playlist contents, with no data deletion, financial impact, or external system execution. The blast radius is limited to a single user's playlist state.
From the tool's definition "Append tracks to an existing playlist" - this action creates/modifies playlist data by adding tracks, which is reversible.
Documented attack patterns abuse exactly the kind of access fw_add_to_playlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for fw_add_to_playlist:
{
"version": "1",
"default": "deny",
"tools": {
"fw_add_to_playlist": {
"limits": [
{
"counter": "fw_add_to_playlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} fw_add_to_playlist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Append tracks to an existing playlist. track_ids are integer Funkwhale track IDs (from fw_search type=. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for fw_add_to_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_add_to_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fw_add_to_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_add_to_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_add_to_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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.