Seeks to the given position in the user’s currently playing track. 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.
AI agents call me.player.seek.update to retrieve information from Spotify without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though me.player.seek.update only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
me.player.seek.update:
rules:
- action: allowSee the full Spotify policy for all 46 tools.
Agents calling read-class tools like me.player.seek.update have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Seeks to the given position in the user’s currently playing track. 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 Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for me.player.seek.update. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spotify MCP server.
me.player.seek.update is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the me.player.seek.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.
Set action: deny in the Intercept policy for me.player.seek.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.
me.player.seek.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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept