Search Spotify
AI agents call search_spotify_catalog to retrieve information from Your Spotify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches data from Spotify's catalog—a read-only operation with no side effects. Users can search for tracks, artists, or albums, but the tool does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal; at worst, an agent could perform excessive searches, but this would not compromise user data or trigger irreversible actions.
From the tool's definition Tool name 'search_spotify_catalog' and description 'Search Spotify' indicate a query operation that retrieves data from Spotify's public catalog without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Search Spotify. It is categorised as a Read tool in the Your Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Your Spotify MCP Server MCP server in PolicyLayer and add a rule for search_spotify_catalog: 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.
search_spotify_catalog 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_catalog 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_catalog. 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_catalog 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.
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 →