sort_uris_by_kind
Sort Spotify references into deterministic groups by entity kind (track, album, artist, playlist, show, episode, audiobook, user) and return them labelled per group — offline.
This record as markdown: /tools/novalux12-spotify-mcp/sort-uris-by-kind.md
What sort_uris_by_kind does on Spotify
AI agents call sort_uris_by_kind to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sort_uris_by_kind is rated Low
Even though sort_uris_by_kind only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sort_uris_by_kind safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sort_uris_by_kind, this is the rule to start with:
sort_uris_by_kind is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every sort_uris_by_kind call is checked against it from then on.
Questions about sort_uris_by_kind
Sort Spotify references into deterministic groups by entity kind (track, album, artist, playlist, show, episode, audiobook, user) and return them labelled per group — offline. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP server in PolicyLayer and add a rule for sort_uris_by_kind: 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.
sort_uris_by_kind is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sort_uris_by_kind 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 sort_uris_by_kind. 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.
sort_uris_by_kind is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spotify, and thousands of servers like it.
This server
Across the catalogue