spotify_like_current_track · Spotify MCP Server MCP

WHAT IT DOES

What spotify_like_current_track does on Spotify MCP Server

AI agents use spotify_like_current_track to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.

WHY IT NEEDS A POLICY

Why spotify_like_current_track needs a policy

This tool modifies user data by adding a track to a library collection. This is a Write operation because it creates/modifies data reversibly (the user can unlike a song to undo the action). It is not Destructive because the action is reversible.

From the tool's definition The tool description states it will 'Add the currently playing track to your Liked Songs,' which is a reversible modification operation that creates a new entry in the user's library.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_like_current_track Rate-limited

spotify_like_current_track stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_like_current_track": {
      "limits": [
        {
          "counter": "spotify_like_current_track_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_like_current_track

What does the spotify_like_current_track tool do? +

Add the currently playing track to your Liked Songs. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spotify_like_current_track? +

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

spotify_like_current_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit spotify_like_current_track? +

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

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

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