listening_recap_brief

Produce a one-call recap of your recent listening: headline plays, top artist/track, leaderboard leaders, peak hour, busiest weekday, discovery ratio, and streak status (default 200 history items; hour and weekday figures are UTC). Quota: GET /me/player/recently-played + 4× GET /me/top/*.

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/listening-recap-brief.md

WHAT IT DOES

What listening_recap_brief does on Spotify

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

Tool retrieves and aggregates user listening data via read-only API calls without side effects.

From the tool's definition Produce recap of recent listening, GET requests, no modifications

Attacks that exploit this kind of access

RECOMMENDED RULE

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

listening_recap_brief Allowed

listening_recap_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": {
    "listening_recap_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 listening_recap_brief call is checked against it from then on.

FAQ

Questions about listening_recap_brief

What does the listening_recap_brief tool do? +

How do I enforce a policy on listening_recap_brief? +

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

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

Can I rate-limit listening_recap_brief? +

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

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

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