spotify_play · Spotify MCP: Risk & Policy

WHAT IT DOES

What spotify_play does on Spotify

AI agents invoke spotify_play to trigger actions in Spotify. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why spotify_play needs a policy

While playback control is reversible (unlike Destructive actions), it executes a command that controls an external service and produces effects beyond data modification. This fits Execute: runs operations whose consequences depend on the execution context. Severity is medium because misuse could disrupt user experience or play unwanted content, but lacks the blast radius of financial transactions or data deletion.

From the tool's definition Tool is 'spotify_play' which 'Start or resume playback on a device' — this triggers external operation (Spotify playback control) whose effects depend on context (which device, what track).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_play Rate-limited

spotify_play stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_play": {
      "limits": [
        {
          "counter": "spotify_play_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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, so you can run agents against it safely.

FAQ

Questions about spotify_play

What does the spotify_play tool do? +

Start or resume playback on a device. It is categorised as a Execute tool in the Spotify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spotify_play? +

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

What risk level is spotify_play? +

spotify_play is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spotify_play? +

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

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

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