play_tracks · Your Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What play_tracks does on Your Spotify MCP Server

AI agents invoke play_tracks to trigger actions in Your 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_tracks needs a policy

This tool initiates playback on an external system (Spotify), which is an external operation/side effect. It doesn't read, write persistent data, or delete anything, but it does execute a command that controls device playback state. Classified as Execute rather than Write because it triggers an operational action rather than creating or modifying stored data.

From the tool's definition 'Start playing specific tracks, an album, or a playlist' — triggers external playback operation on Spotify

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

play_tracks Rate-limited

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

FAQ

Questions about play_tracks

What does the play_tracks tool do? +

Start playing specific tracks, an album, or a playlist. Provide either track URIs or a context URI (album/playlist/artist). Example queries: -. It is categorised as a Execute tool in the Your 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_tracks? +

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

What risk level is play_tracks? +

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

Can I rate-limit play_tracks? +

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

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

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