taste_era_playlist

Era window → representative track list: pick a listening era and get its playlist spec. Read-only, no auth.

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/taste-era-playlist.md

WHAT IT DOES

What taste_era_playlist does on Spotify

AI agents call taste_era_playlist 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 taste_era_playlist is rated Low

Retrieves representative playlist data for a specified listening era without modification or side effects.

From the tool's definition pick a listening era and get its playlist spec. Read-only, no auth.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs taste_era_playlist 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 taste_era_playlist, this is the rule to start with:

taste_era_playlist Allowed

taste_era_playlist 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": {
    "taste_era_playlist": {}
  }
}

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 taste_era_playlist call is checked against it from then on.

FAQ

Questions about taste_era_playlist

What does the taste_era_playlist tool do? +

Era window → representative track list: pick a listening era and get its playlist spec. Read-only, no auth. 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 taste_era_playlist? +

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

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

Can I rate-limit taste_era_playlist? +

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

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

taste_era_playlist 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 538 Spotify tools →

Across the catalogue

The MCP Attack Database →

Guides

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