Medium Risk

fw_add_to_playlist

Append tracks to an existing playlist. track_ids are integer Funkwhale track IDs (from fw_search type=

How to control fw_add_to_playlist ↓

What fw_add_to_playlist does on Crow

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.

Medium Risk

Why fw_add_to_playlist needs a policy

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:

How to control fw_add_to_playlist

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:

policy.json
{
  "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.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fw_add_to_playlist

What does the fw_add_to_playlist tool do? +

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.

How do I enforce a policy on fw_add_to_playlist? +

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.

What risk level is fw_add_to_playlist? +

fw_add_to_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit fw_add_to_playlist? +

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.

How do I block fw_add_to_playlist completely? +

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.

What MCP server provides fw_add_to_playlist? +

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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.