Search Spotify for tracks, albums, and artists
AI agents call search_spotify to retrieve information from Spotify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Searching is a pure query operation that retrieves information from Spotify's catalog without modifying, deleting, or executing any state-changing actions. Even if an AI agent misuses this tool, the worst outcome is excessive queries or discovery of unintended content, causing minimal harm. This fits the Read category's definition of retrieving data without side effects.
From the tool's definition Tool description states 'Search Spotify for tracks, albums, and artists' — a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Search Spotify for tracks, albums, and artists. It is categorised as a Read tool in the Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for search_spotify: 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.
search_spotify 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 search_spotify 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 search_spotify. 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.
search_spotify is provided by the Spotify MCP Server MCP server (nicklaustrup/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 →