High Risk →

spotify_search_and_play_track

Search for a track by name and play it immediately

How to control spotify_search_and_play_track ↓

AI agents invoke spotify_search_and_play_track to trigger actions in Mcp Windows. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

This tool triggers an external operation (searching and playing a track on Spotify), which constitutes executing an action on an external service. It has side effects beyond a simple read — it actively controls media playback. Severity is medium as misuse could disrupt audio playback but poses no data loss or financial risk.

From the tool's definition Search for a track by name and play it immediately

Documented attack patterns abuse exactly the kind of access spotify_search_and_play_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_and_play_track:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "spotify_search_and_play_track": {
      "limits": [
        {
          "counter": "spotify_search_and_play_track_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

spotify_search_and_play_track stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the spotify_search_and_play_track tool do? +

Search for a track by name and play it immediately. It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spotify_search_and_play_track? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for spotify_search_and_play_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_and_play_track? +

spotify_search_and_play_track is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spotify_search_and_play_track? +

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

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

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