get_recently_played

Get recently played tracks with timestamps

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/get-recently-played.md

WHAT IT DOES

What get_recently_played does on Spotify

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

Retrieves playback history data without modifying or executing any actions.

From the tool's definition Get recently played tracks with timestamps

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_recently_played Allowed

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

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

FAQ

Questions about get_recently_played

What does the get_recently_played tool do? +

Get recently played tracks with timestamps. 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 get_recently_played? +

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

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

Can I rate-limit get_recently_played? +

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

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

get_recently_played 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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