reorder_playlist_items
AI agents use reorder_playlist_items to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.
Reordering playlist items is a Write operation as it modifies the order of items in a playlist without deleting any data. The change is reversible since items can be reordered again. Confidence is reduced because the description is empty, but the tool name strongly implies a reorder/rearrangement operation consistent with the Spotify Web API's reorder playlist tracks endpoint.
From the tool's definition Tool name 'reorder_playlist_items' suggests reordering items within a playlist — a reversible modification of playlist order.
Attacks that exploit this kind of access
reorder_playlist_items. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for reorder_playlist_items: 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 MCP Server. Nothing to install.
reorder_playlist_items 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 reorder_playlist_items 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 reorder_playlist_items. 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.
reorder_playlist_items is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). 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 →