saved_albums_by_decade

Group your saved albums by release decade (from each album release_date) and show a histogram. Read-only.

SERVERSpotify SOURCE@novalux12/spotify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/saved-albums-by-decade.md

WHAT IT DOES

What saved_albums_by_decade does on Spotify

AI agents call saved_albums_by_decade to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why saved_albums_by_decade is rated Low

Even though saved_albums_by_decade only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs saved_albums_by_decade safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For saved_albums_by_decade, this is the rule to start with:

saved_albums_by_decade Allowed

saved_albums_by_decade is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "saved_albums_by_decade": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every saved_albums_by_decade call is checked against it from then on.

FAQ

Questions about saved_albums_by_decade

What does the saved_albums_by_decade tool do? +

Group your saved albums by release decade (from each album release_date) and show a histogram. Read-only. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on saved_albums_by_decade? +

Register the Spotify MCP server in PolicyLayer and add a rule for saved_albums_by_decade: 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. Nothing to install.

What risk level is saved_albums_by_decade? +

saved_albums_by_decade is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit saved_albums_by_decade? +

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

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

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

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 544 Spotify tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →