spotify_resume_last_played
Resume last playlist or album
This record as markdown: /tools/mukul975-mcp-windows-automation/spotify-resume-last-played.md
What spotify_resume_last_played does on Mcp Windows
AI agents invoke spotify_resume_last_played 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.
Why spotify_resume_last_played is rated High
This tool triggers an external operation on the Spotify application — resuming playback. It doesn't just read data, nor does it write/delete persistent data or involve finances. It executes a playback control action on an external media service.
From the tool's definition Resume last playlist or album
Attacks that exploit this kind of access
The rule that runs spotify_resume_last_played safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_resume_last_played, this is the rule to start with:
spotify_resume_last_played 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every spotify_resume_last_played call is checked against it from then on.
Questions about spotify_resume_last_played
Resume last playlist or album. 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.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for spotify_resume_last_played: 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.
spotify_resume_last_played is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spotify_resume_last_played 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.
Set action: deny in the PolicyLayer policy for spotify_resume_last_played. 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.
spotify_resume_last_played 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.
More on Mcp Windows, and thousands of servers like it.
Across the catalogue