create_playlist_from_query · Your Spotify MCP Server MCP

WHAT IT DOES

What create_playlist_from_query does on Your Spotify MCP Server

AI agents use create_playlist_from_query to create or update resources in Your Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Your Spotify MCP Server environment.

WHY IT NEEDS A POLICY

Why create_playlist_from_query needs a policy

This tool creates a new, reversible resource (a Spotify playlist). It does not execute arbitrary code, delete data, move money, or cause irreversible harm. The severity is medium because creating unwanted playlists could clutter a user's account and potentially expose listening data through public playlists, but the action is fully reversible by deletion.

From the tool's definition Tool description states 'Create a new Spotify playlist' and 'turning Your Spotify analytics results into playable playlists'. The verb 'Create' and action of making a new playlist object indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_playlist_from_query Rate-limited

create_playlist_from_query 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_playlist_from_query": {
      "limits": [
        {
          "counter": "create_playlist_from_query_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Your Spotify MCP Server, so you can run agents against it safely.

FAQ

Questions about create_playlist_from_query

What does the create_playlist_from_query tool do? +

Create a new Spotify playlist from track URIs. Perfect for turning Your Spotify analytics results into playable playlists. Example queries: -. It is categorised as a Write tool in the Your Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_playlist_from_query? +

Register the Your Spotify MCP Server MCP server in PolicyLayer and add a rule for create_playlist_from_query: 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 Your Spotify MCP Server. Nothing to install.

What risk level is create_playlist_from_query? +

create_playlist_from_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_playlist_from_query? +

Yes. Add a rate_limit block to the create_playlist_from_query 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.

How do I block create_playlist_from_query completely? +

Set action: deny in the PolicyLayer policy for create_playlist_from_query. 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 create_playlist_from_query? +

create_playlist_from_query is provided by the Your Spotify MCP Server MCP server (pentafive/your-spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.