play_track · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What play_track does on Spotify MCP Server

AI agents invoke play_track 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 play_track needs a policy

This tool executes an action on an external system (Spotify playback), causing a real-world side effect (starting audio playback). It is not a simple data read or write, but an execution of an operation that changes the state of a media player. Misuse could cause unexpected audio playback in sensitive environments, but the blast radius is limited.

From the tool's definition 'Play a specific track by its URI or ID' — triggers external playback operation on Spotify

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

play_track Rate-limited

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

What does the play_track tool do? +

Play a specific track by its URI or ID. 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 play_track? +

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

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

Can I rate-limit play_track? +

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

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

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