add_to_queue · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_to_queue does on Spotify MCP Server

AI agents use 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 add_to_queue needs a policy

This tool modifies the playback queue by adding items to it. Queue modifications are reversible (items can be removed or the queue cleared), causing no permanent data loss or external financial/destructive effects. It is a Write operation with low severity since misuse would only affect the current playback session and can easily be corrected.

From the tool's definition Tool name 'add_to_queue' and description 'Add a track or episode to the playback queue' indicate creation/modification of the queue state, which is reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_to_queue Rate-limited

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": {
    "add_to_queue": {
      "limits": [
        {
          "counter": "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 add_to_queue

What does the add_to_queue tool do? +

Add a track or episode to the playback queue. 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 add_to_queue? +

Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for 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 add_to_queue? +

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 add_to_queue? +

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

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

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