Get the current user's saved episodes.
AI agents call get_saved_episodes to retrieve information from Spotify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or fetches the user's saved podcast episodes from their Spotify library. It performs a read-only query operation with no ability to modify, delete, or trigger external side effects. The blast radius of misuse is minimal—an AI agent could only access the user's saved episode list, which is already data the authenticated user has authorized access to.
From the tool's definition Tool name 'get_saved_episodes' and description 'Get the current user's saved episodes' indicate a retrieval operation that queries user data without modification or side effects.
Attacks that exploit this kind of access
Get the current user's saved episodes. It is categorised as a Read tool in the Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for get_saved_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 MCP Server. Nothing to install.
get_saved_episodes 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 get_saved_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 get_saved_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.
get_saved_episodes is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →