spotify_previous · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What spotify_previous does on Spotify MCP Server

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

This tool performs a playback control operation (skipping to the previous track), which is an external operation that affects the state of Spotify playback. It's not a simple read, nor does it create/modify stored data or delete anything. It executes a command that changes the playback state, making Execute the most appropriate category. The blast radius is low since it only affects music playback.

From the tool's definition 'Skip to the previous track' — triggers a playback control action on an external Spotify device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_previous Rate-limited

spotify_previous 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_previous": {
      "limits": [
        {
          "counter": "spotify_previous_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_previous

What does the spotify_previous tool do? +

Skip to the previous track in the user. 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_previous? +

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

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

Can I rate-limit spotify_previous? +

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

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

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