spotify_playlist
Retrieve Spotify playlist details. Returns normalized Spotify Web Player playlist metadata and items from Spotify's fetchPlaylist Pathfinder response. Provide either uri or id; defaults to a known public playlist when omitted.
This record as markdown: /tools/crawlora-mcp/spotify-playlist.md
What spotify_playlist does on Crawlora
AI agents call spotify_playlist to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Spotify playlist ID. Used when uri is omitted |
uri | string | — | Spotify playlist URI or open.spotify.com playlist URL |
limit | integer | — | Playlist item limit, clamped to 1-50 |
offset | integer | — | Playlist item offset |
enable_watch_feed_entrypoint | boolean | — | Enable watch feed entrypoint |
include_episode_content_ratings_v2 | boolean | — | Include Spotify episode content ratings v2 |
Parameters from the server's own tool schema.
Why spotify_playlist is rated Low
Even though spotify_playlist only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (uri)
Attacks that exploit this kind of access
The rule that runs spotify_playlist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_playlist, this is the rule to start with:
spotify_playlist is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every spotify_playlist call is checked against it from then on.
Questions about spotify_playlist
Retrieve Spotify playlist details. Returns normalized Spotify Web Player playlist metadata and items from Spotify's fetchPlaylist Pathfinder response. Provide either uri or id; defaults to a known public playlist when omitted. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
spotify_playlist accepts 6 parameters: id, uri, limit, offset, enable_watch_feed_entrypoint, include_episode_content_ratings_v2. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for spotify_playlist: 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 Crawlora. Nothing to install.
spotify_playlist 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_playlist 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_playlist. 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_playlist is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue