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

spotify_open_release_radar

Open Release Radar playlist

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-open-release-radar.md

What spotify_open_release_radar does on Mcp Windows

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

This tool executes a system-level action to open the Spotify application or browser to a specific playlist. It's an external operation with side effects (launching/switching focus of an application), fitting the Execute category. The blast radius is medium since it affects the user's active session but doesn't modify data.

From the tool's definition Open Release Radar playlist — triggers an external operation (opening a Spotify playlist) on the Windows system

Questions about spotify_open_release_radar

What does the spotify_open_release_radar tool do? +

Open Release Radar playlist. 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_open_release_radar? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for spotify_open_release_radar: 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_open_release_radar? +

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

Can I rate-limit spotify_open_release_radar? +

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

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

spotify_open_release_radar 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.