Medium Risk

me.player.queue.create

Add an item to be played next in the user's current playback queue. This API only works for users who have Spotify Premium. The order of execution is not guaranteed when you use this API with other Player API endpoints.

Accepts URL/endpoint input (uri)

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

arjunkmrm/spotify Write Risk 2/5

AI agents use me.player.queue.create to create or modify resources in Spotify. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call me.player.queue.create repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Spotify.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

arjunkmrm-spotify.yaml
tools:
  me.player.queue.create:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Spotify policy for all 46 tools.

Tool Name me.player.queue.create
Category Write
MCP Server Spotify MCP Server
Risk Level Medium

View all 46 tools →

Agents calling write-class tools like me.player.queue.create 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 Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the me.player.queue.create tool do? +

Add an item to be played next in the user's current playback queue. This API only works for users who have Spotify Premium. The order of execution is not guaranteed when you use this API with other Player API endpoints. . 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.

How do I enforce a policy on me.player.queue.create? +

Add a rule in your Intercept YAML policy under the tools section for me.player.queue.create. 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 me.player.queue.create? +

me.player.queue.create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit me.player.queue.create? +

Yes. Add a rate_limit block to the me.player.queue.create 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 me.player.queue.create completely? +

Set action: deny in the Intercept policy for me.player.queue.create. 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 me.player.queue.create? +

me.player.queue.create 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.