search_deep

Paged catalog search that walks past the API limit of 10 results per type. Fetches up to 5 pages of 10 results per requested type server-side from a caller-supplied

SERVERSpotify SOURCE@novalux12/spotify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/search-deep.md

WHAT IT DOES

What search_deep does on Spotify

AI agents call search_deep 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.

RISK

Why search_deep is rated Low

Retrieves data from Spotify catalog with pagination; read-only operation with no side effects.

From the tool's definition Paged catalog search, fetches results, no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_deep 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 search_deep, this is the rule to start with:

search_deep Allowed

search_deep is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_deep": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every search_deep call is checked against it from then on.

FAQ

Questions about search_deep

What does the search_deep tool do? +

Paged catalog search that walks past the API limit of 10 results per type. Fetches up to 5 pages of 10 results per requested type server-side from a caller-supplied. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_deep? +

Register the Spotify MCP server in PolicyLayer and add a rule for search_deep: 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.

What risk level is search_deep? +

search_deep is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_deep? +

Yes. Add a rate_limit block to the search_deep 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.

How do I block search_deep completely? +

Set action: deny in the PolicyLayer policy for search_deep. 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.

What MCP server provides search_deep? +

search_deep 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.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →