Low Risk

playlists.items.list

Get full details of the items of a playlist owned by a Spotify user. **Note**: This endpoint is only accessible for playlists owned by the current user or playlists the user is a collaborator of. A `403 Forbidden` status code will be returned if the user is neither the owner nor a collaborator o...

Part of the Spotify MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call playlists.items.list to retrieve information from Spotify without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though playlists.items.list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

arjunkmrm-spotify.yaml
tools:
  playlists.items.list:
    rules:
      - action: allow

See the full Spotify policy for all 46 tools.

Tool Name playlists.items.list
Category Read
MCP Server Spotify MCP Server
Risk Level Low

View all 46 tools →

Agents calling read-class tools like playlists.items.list have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the playlists.items.list tool do? +

Get full details of the items of a playlist owned by a Spotify user. **Note**: This endpoint is only accessible for playlists owned by the current user or playlists the user is a collaborator of. A `403 Forbidden` status code will be returned if the user is neither the owner nor a collaborator of the playlist. . It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on playlists.items.list? +

Add a rule in your Intercept YAML policy under the tools section for playlists.items.list. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spotify MCP server.

What risk level is playlists.items.list? +

playlists.items.list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit playlists.items.list? +

Yes. Add a rate_limit block to the playlists.items.list rule in your Intercept 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.

How do I block playlists.items.list completely? +

Set action: deny in the Intercept policy for playlists.items.list. 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.

What MCP server provides playlists.items.list? +

playlists.items.list is provided by the Spotify MCP server (arjunkmrm/spotify). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Spotify

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.