Create a new Spotify playlist for the current user.
AI agents use create_playlist to create or update resources in Mcp Spotify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Spotify environment.
This tool creates new data (a playlist) in the user's Spotify account, making it a Write operation rather than Read. The severity is medium because while playlist creation is reversible (playlists can be deleted), it modifies user account state and could clutter the account or be used for spam.
From the tool's definition Tool creates a new playlist, which is a data modification operation. Description states 'Create a new Spotify playlist for the current user' — the verb 'create' indicates a write operation that adds new data to the user's account.
Attacks that exploit this kind of access
Create a new Spotify playlist for the current user. It is categorised as a Write tool in the Mcp Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp 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 Mcp 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 Mcp Spotify MCP server (obrien-matthew/mcp-spotify). 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 →