spotify_add_to_queue · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What spotify_add_to_queue does on Spotify MCP Server

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

WHY IT NEEDS A POLICY

Why spotify_add_to_queue needs a policy

Adding a track to a queue is a write operation that modifies user data (the queue) but is fully reversible—the user can remove tracks from the queue. It does not execute arbitrary code, delete data permanently, or involve financial transactions. Blast radius is low since queue modifications are non-destructive and easily undone.

From the tool's definition Tool name is 'spotify_add_to_queue' and description states 'Add a track to the user' (likely 'to the user's queue'). This creates a new queue entry, modifying the playback queue state reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_add_to_queue Rate-limited

spotify_add_to_queue 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": {
    "spotify_add_to_queue": {
      "limits": [
        {
          "counter": "spotify_add_to_queue_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 Spotify MCP Server, so you can run agents against it safely.

FAQ

Questions about spotify_add_to_queue

What does the spotify_add_to_queue tool do? +

Add a track to the user. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spotify_add_to_queue? +

Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for spotify_add_to_queue: 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 Spotify MCP Server. Nothing to install.

What risk level is spotify_add_to_queue? +

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

Can I rate-limit spotify_add_to_queue? +

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

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

spotify_add_to_queue is provided by the Spotify MCP Server MCP server (llmtooling/spotify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.