control_playback · Your Spotify MCP Server MCP

WHAT IT DOES

What control_playback does on Your Spotify MCP Server

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

This tool executes real-time control commands on an external Spotify playback device. It is not merely reading data nor creating/modifying stored data; it triggers live operational effects (changing playback state, volume, track position) on an external system. It spans Execute rather than Write because effects are transient runtime actions, not persistent data changes.

From the tool's definition 'Control your Spotify playback' with actions: play, pause, next, previous, seek, volume — triggers external operations on a live Spotify playback session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

control_playback Rate-limited

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

What does the control_playback tool do? +

Control your Spotify playback. Available actions: play, pause, next, previous, seek, volume. 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 control_playback? +

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

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

Can I rate-limit control_playback? +

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

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

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