save_to_library · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_to_library does on Spotify MCP Server

AI agents use save_to_library 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 save_to_library needs a policy

This tool modifies user state by adding items to a library, but the operation is reversible (items can be removed). It has no destructive or financial impact. The severity is medium because while the blast radius is limited to one user's library preferences, an AI agent could spam or maliciously clutter a user's saved library with unwanted content, reducing usability of their music service.

From the tool's definition Tool description states it "Save[s] items (tracks/albums/shows/episodes/audiobooks) to the user's library" — a clear modification action that adds data to a user's persistent collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_to_library Rate-limited

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

What does the save_to_library tool do? +

Save items (tracks/albums/shows/episodes/audiobooks) to the user's library. 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 save_to_library? +

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

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

Can I rate-limit save_to_library? +

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

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

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