spotify_profile_playlists
Retrieve Spotify public profile playlists. Returns normalized public playlists from Spotify's Web Player user-profile service. Provide username, uri, or url; defaults to Spotify's official profile.
This record as markdown: /tools/crawlora-mcp/spotify-profile-playlists.md
What spotify_profile_playlists does on Crawlora
AI agents call spotify_profile_playlists 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 |
|---|---|---|---|
uri | string | — | Spotify user URI |
url | string | — | open.spotify.com user URL |
limit | integer | — | Playlist limit, clamped to 1-50 |
offset | integer | — | Playlist offset |
username | string | — | Spotify username |
Parameters from the server's own tool schema.
Why spotify_profile_playlists is rated Low
Even though spotify_profile_playlists 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_profile_playlists 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_profile_playlists, this is the rule to start with:
spotify_profile_playlists 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_profile_playlists call is checked against it from then on.
Questions about spotify_profile_playlists
Retrieve Spotify public profile playlists. Returns normalized public playlists from Spotify's Web Player user-profile service. Provide username, uri, or url; defaults to Spotify's official profile. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
spotify_profile_playlists accepts 5 parameters: uri, url, limit, offset, username. 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_profile_playlists: 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_profile_playlists 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_profile_playlists 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_profile_playlists. 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_profile_playlists 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