taste_weekly_recap

Week-in-review brief: stream count, top artists/tracks of the window, busiest day, novelty share. 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-weekly-recap.md

WHAT IT DOES

What taste_weekly_recap does on Spotify

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

Tool retrieves user listening statistics and summaries without modifying data or requiring authentication.

From the tool's definition Week-in-review brief, stream count, top artists/tracks, read-only, no auth

Attacks that exploit this kind of access

RECOMMENDED RULE

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

taste_weekly_recap Allowed

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

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

FAQ

Questions about taste_weekly_recap

What does the taste_weekly_recap tool do? +

Week-in-review brief: stream count, top artists/tracks of the window, busiest day, novelty share. 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_weekly_recap? +

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

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

Can I rate-limit taste_weekly_recap? +

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

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

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