New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

spotify_resume_last_played

Resume last playlist or album

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation
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/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

Questions about spotify_resume_last_played

What does the spotify_resume_last_played tool do? +

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.

How do I enforce a policy on spotify_resume_last_played? +

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.

What risk level is spotify_resume_last_played? +

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

Can I rate-limit spotify_resume_last_played? +

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.

How do I block spotify_resume_last_played completely? +

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.

What MCP server provides spotify_resume_last_played? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Windows's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.