play_at

Start playback at a specific position — accepts H:MM:SS / MM:SS / seconds string or position_ms. Wraps PUT /me/player/play with offset/position_ms. 🟢 (1 write).

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/play-at.md

WHAT IT DOES

What play_at does on Spotify

AI agents invoke play_at 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 play_at is rated High

play_at triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

play_at Rate-limited

play_at 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": {
    "play_at": {
      "limits": [
        {
          "counter": "play_at_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 play_at call is checked against it from then on.

FAQ

Questions about play_at

What does the play_at tool do? +

Start playback at a specific position — accepts H:MM:SS / MM:SS / seconds string or position_ms. Wraps PUT /me/player/play with offset/position_ms. 🟢 (1 write). 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 play_at? +

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

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

Can I rate-limit play_at? +

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

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

play_at 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 544 Spotify tools → High-risk tools on this server →

Across the catalogue

music_play on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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