previous_track · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What previous_track does on Spotify MCP Server

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

This tool triggers an external operation on Spotify playback (navigating to the previous track). It causes a side effect on the Spotify player state but does not read, write, or delete data, nor does it involve financial transactions. It fits Execute as it controls an external system's behavior.

From the tool's definition Go back to the previous track

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

previous_track Rate-limited

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

What does the previous_track tool do? +

Go back to the previous track. 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 previous_track? +

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

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

Can I rate-limit previous_track? +

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

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

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