High Risk →

me.player.play.update

Start a new context or resume current playback on the user's active device. This API only works for users who have Spotify Premium. The order of execution is not guaranteed when you use this API with other Player API endpoints.

Part of the Spotify MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

arjunkmrm/spotify Execute Risk 3/5

AI agents invoke me.player.play.update to trigger processes or run actions in Spotify. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

me.player.play.update can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

arjunkmrm-spotify.yaml
tools:
  me.player.play.update:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Spotify policy for all 46 tools.

Tool Name me.player.play.update
Category Execute
MCP Server Spotify MCP Server
Risk Level High

View all 46 tools →

Agents calling execute-class tools like me.player.play.update have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

me.player.play.update is one of the high-risk operations in Spotify. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the me.player.play.update tool do? +

Start a new context or resume current playback on the user's active device. This API only works for users who have Spotify Premium. The order of execution is not guaranteed when you use this API with other Player API endpoints. . 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 me.player.play.update? +

Add a rule in your Intercept YAML policy under the tools section for me.player.play.update. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spotify MCP server.

What risk level is me.player.play.update? +

me.player.play.update is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit me.player.play.update? +

Yes. Add a rate_limit block to the me.player.play.update rule in your Intercept 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 me.player.play.update completely? +

Set action: deny in the Intercept policy for me.player.play.update. 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 me.player.play.update? +

me.player.play.update is provided by the Spotify MCP server (arjunkmrm/spotify). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Spotify

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.