apply_scene

Apply a saved scene: resolve its device hint, transfer playback, then set volume/shuffle/repeat and start the saved context (in that order; missing targets are skipped)

SERVERSpotify SOURCE@novalux12/spotify-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/apply-scene.md

WHAT IT DOES

What apply_scene does on Spotify

AI agents invoke apply_scene to trigger actions in Spotify. 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.

RISK

Why apply_scene is rated High

Triggers multiple external Spotify playback operations in sequence, affecting active device state.

From the tool's definition transfer playback, set volume/shuffle/repeat and start the saved context

Attacks that exploit this kind of access

RECOMMENDED RULE

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

apply_scene Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "apply_scene": {
      "limits": [
        {
          "counter": "apply_scene_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about apply_scene

What does the apply_scene tool do? +

Apply a saved scene: resolve its device hint, transfer playback, then set volume/shuffle/repeat and start the saved context (in that order; missing targets are skipped). It is categorised as a Execute tool in the Spotify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on apply_scene? +

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

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

Can I rate-limit apply_scene? +

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

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

apply_scene 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →