spotify_play · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What spotify_play does on Spotify MCP Server

AI agents invoke spotify_play to trigger actions in Spotify MCP Server. 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

This tool executes a command on an external service (Spotify) that produces observable side effects. While not destructive or financial, it performs an action beyond mere data retrieval. The severity is medium because misuse could disrupt the user's intended activities or trigger unexpected audio playback, though the operation is reversible (can be paused/stopped).

From the tool's definition Tool description states "Start playback on the user's active device" — this triggers an external operation (audio playback) whose effects depend on the state of the user's Spotify account and active device.

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

FAQ

Questions about spotify_play

What does the spotify_play tool do? +

Start playback on the user's active device. It is categorised as a Execute tool in the Spotify MCP Server 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 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 MCP Server. 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 MCP server (mfteloglu/spotify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.