AI agents invoke play_favorite_song 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.
This tool executes an external operation by launching or controlling a browser to navigate to YouTube and play media. It has side effects beyond reading data (opens application, triggers playback, potentially modifies browser state), placing it in the Execute category. Severity is medium because misuse could disrupt user activity or play unwanted content, but it has limited destructive potential.
From the tool's definition 'Play user's favorite song on YouTube' — triggers an external browser/application action to open and play content on YouTube
Documented attack patterns abuse exactly the kind of access play_favorite_song gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for play_favorite_song:
{
"version": "1",
"default": "deny",
"tools": {
"play_favorite_song": {
"limits": [
{
"counter": "play_favorite_song_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}play_favorite_song 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.
Free to start. No card required.
Play user's favorite song on YouTube. 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 play_favorite_song: 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.
play_favorite_song 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 play_favorite_song 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 play_favorite_song. 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.
play_favorite_song 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.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.