taste_daily_brief

Yesterday (or a given date) in brief: top-3 tracks, 2 revival picks, novelty share vs the lifetime core. 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-daily-brief.md

WHAT IT DOES

What taste_daily_brief does on Spotify

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

Tool retrieves and summarizes historical listening data without modifying or executing external operations.

From the tool's definition top-3 tracks, 2 revival picks, novelty share, Read-only, no auth.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

taste_daily_brief Allowed

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

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

FAQ

Questions about taste_daily_brief

What does the taste_daily_brief tool do? +

Yesterday (or a given date) in brief: top-3 tracks, 2 revival picks, novelty share vs the lifetime core. 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_daily_brief? +

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

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

Can I rate-limit taste_daily_brief? +

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

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

taste_daily_brief 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 →