AI agents use create-playlist to create or update resources in Spotify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify environment.
Creating a playlist modifies the user's account state by adding a new resource, but the action is reversible (playlists can be deleted). This falls squarely into the Write category. Severity is medium because misuse could result in creation of numerous unwanted playlists, but the impact is limited to the user's own account and can be undone.
From the tool's definition Tool name 'create-playlist' and description 'Create a new playlist' indicate the tool creates new data in the user's Spotify account. This is a Write operation that adds a reversible resource.
Documented attack patterns abuse exactly the kind of access create-playlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spotify, and nothing reaches the server without passing your rules. This is the rule we recommend for create-playlist:
{
"version": "1",
"default": "deny",
"tools": {
"create-playlist": {
"limits": [
{
"counter": "create-playlist_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-playlist stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new playlist. It is categorised as a Write tool in the Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP server in PolicyLayer and add a rule for create-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 Spotify. Nothing to install.
create-playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-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 create-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.
create-playlist is provided by the Spotify MCP server (qchuchu/spotify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Spotify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Spotify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.