add_tracks_to_playlist · Soundcloud MCP: Risk & Policy

WHAT IT DOES

What add_tracks_to_playlist does on Soundcloud

AI agents use add_tracks_to_playlist to create or update resources in Soundcloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Soundcloud environment.

WHY IT NEEDS A POLICY

Why add_tracks_to_playlist needs a policy

This tool creates or modifies data (playlist membership) in a reversible manner — tracks can be removed later. It does not execute arbitrary code, delete data irreversibly, or commit financial transactions. It is a straightforward Write operation. Severity is medium because misuse could clutter playlists or cause inconvenience, but the action is easily undone via remove_track_from_playlist.

From the tool's definition Tool description states 'Append tracks to an existing SoundCloud playlist' — this modifies playlist data by adding content. The verb 'append' and 'without replacing' confirm it creates/modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tracks_to_playlist Rate-limited

add_tracks_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_tracks_to_playlist": {
      "limits": [
        {
          "counter": "add_tracks_to_playlist_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Soundcloud, so you can run agents against it safely.

FAQ

Questions about add_tracks_to_playlist

What does the add_tracks_to_playlist tool do? +

Append tracks to an existing SoundCloud playlist without replacing existing ones. It is categorised as a Write tool in the Soundcloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_tracks_to_playlist? +

Register the Soundcloud MCP server in PolicyLayer and add a rule for add_tracks_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 Soundcloud. Nothing to install.

What risk level is add_tracks_to_playlist? +

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

Can I rate-limit add_tracks_to_playlist? +

Yes. Add a rate_limit block to the add_tracks_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 add_tracks_to_playlist completely? +

Set action: deny in the PolicyLayer policy for add_tracks_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 add_tracks_to_playlist? +

add_tracks_to_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.