spotify_search
Search Spotify for tracks, albums, artists, or playlists.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/spotify-search.md
What spotify_search does on UnClick
AI agents call spotify_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Comma-separated: track, album, artist, playlist (default: track) |
limit | number | — | |
query | string | Yes | |
market | string | — | |
offset | number | — | |
bearer_token | string | Yes |
Parameters from the server's own tool schema.
Why spotify_search is rated Low
This tool performs a search operation, which is a read-only retrieval of information from Spotify's catalog. No data is created, modified, deleted, or executed. The search parameters are constrained to music-related entities (tracks, albums, artists, playlists), minimizing potential for misuse.
From the tool's definition Tool name 'spotify_search' and description 'Search Spotify for tracks, albums, artists, or playlists' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs spotify_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_search, this is the rule to start with:
spotify_search 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 UnClick, apply this rule, and every spotify_search call is checked against it from then on.
Questions about spotify_search
Search Spotify for tracks, albums, artists, or playlists. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
spotify_search accepts 6 parameters: type, limit, query, market, offset, bearer_token. Required: query, bearer_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for spotify_search: 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 UnClick. Nothing to install.
spotify_search 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 spotify_search 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 spotify_search. 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.
spotify_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue