play · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What play does on Spotify MCP Server

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

The tool name 'play' on a server that explicitly offers playback control strongly suggests this triggers external playback operations on Spotify (starting/resuming music playback). This is an Execute-category action as it triggers an external operation. The description is empty, which lowers confidence.

From the tool's definition Tool name is 'play' on a Spotify MCP server described as having tools to 'control playback'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

play Rate-limited

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

What does the play tool do? +

play. 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? +

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

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

Can I rate-limit play? +

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

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

play 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.

// THE FULL RECORD

play is one line of Spotify MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →