Get the user's recently played tracks with timestamps.
AI agents call spotify_recently_played to retrieve information from Spotify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation that queries Spotify's history of tracks the user has played. It has no side effects, does not modify any state, and poses minimal risk even if called unexpectedly by an AI agent. The worst outcome would be revealing the user's listening history to the agent, which is a privacy concern but not operationally destructive.
From the tool's definition Tool retrieves user's recently played tracks with timestamps. The description explicitly indicates a query/retrieval operation ("Get the user's") with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access spotify_recently_played gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spotify, and nothing reaches the server without passing your rules. This is the rule we recommend for spotify_recently_played:
{
"version": "1",
"default": "deny",
"tools": {
"spotify_recently_played": {}
}
}spotify_recently_played is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the user's 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.
Register the Spotify MCP server in PolicyLayer and add a rule for spotify_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.
spotify_recently_played is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spotify_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.
Set action: deny in the PolicyLayer policy for spotify_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.
spotify_recently_played is provided by the Spotify MCP server (veridyia/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Spotify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Spotify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.