Low Risk

spotify_search_track

Search for a track by name in Spotify

How to control spotify_search_track ↓

AI agents call spotify_search_track to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a read-only search query against Spotify's music catalog. It retrieves information about tracks matching search criteria but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal - worst case would be noisy search queries or API rate limiting.

From the tool's definition Tool description states "Search for a track by name in Spotify" - a query operation that retrieves data without modifying state or triggering external actions beyond read-only search.

Documented attack patterns abuse exactly the kind of access spotify_search_track gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for spotify_search_track:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "spotify_search_track": {}
  }
}

spotify_search_track is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the spotify_search_track tool do? +

Search for a track by name in Spotify. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spotify_search_track? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for spotify_search_track: 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 Mcp Windows. Nothing to install.

What risk level is spotify_search_track? +

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

Can I rate-limit spotify_search_track? +

Yes. Add a rate_limit block to the spotify_search_track 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 spotify_search_track completely? +

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

spotify_search_track is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.