archive_played_episodes
Remove fully-played episodes from your episode library in bulk (checks resume_point.fully_played). Batch DELETE /me/library; archives over 50 episodes require elicitation confirmation (or SPOTIFY_MCP_CONFIRM=never for automation). PREVIEWS BY DEFAULT — pass dry_run=false to commit. Returns a remo...
This record as markdown: /tools/novalux12-spotify-mcp/archive-played-episodes.md
What archive_played_episodes does on Spotify
AI agents call archive_played_episodes to permanently remove resources in Spotify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why archive_played_episodes is rated Critical
Bulk deletes episodes from library; though revertible via undo, it's a mass destructive operation.
From the tool's definition Remove fully-played episodes... Batch DELETE /me/library
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs archive_played_episodes 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 archive_played_episodes, this is the rule to start with:
archive_played_episodes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every archive_played_episodes call is checked against it from then on.
Questions about archive_played_episodes
Remove fully-played episodes from your episode library in bulk (checks resume_point.fully_played). Batch DELETE /me/library; archives over 50 episodes require elicitation confirmation (or SPOTIFY_MCP_CONFIRM=never for automation). PREVIEWS BY DEFAULT — pass dry_run=false to commit. Returns a removal receipt (resolvable via verify_receipt, revertible via undo_mutation). It is categorised as a Destructive tool in the Spotify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Spotify MCP server in PolicyLayer and add a rule for archive_played_episodes: 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.
archive_played_episodes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archive_played_episodes 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 archive_played_episodes. 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.
archive_played_episodes 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.
More on Spotify, and thousands of servers like it.
Across the catalogue