spotify_dislike_track
Dislike the current track (for recommendation training)
This record as markdown: /tools/mukul975-mcp-windows-automation/spotify-dislike-track.md
What spotify_dislike_track does on Mcp Windows
AI agents use spotify_dislike_track to create or update resources in Mcp Windows, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
Why spotify_dislike_track is rated Medium
This tool modifies a user preference/rating in Spotify's recommendation system. It's a reversible write operation (likes/dislikes can typically be changed), affecting only user preferences with minimal blast radius.
From the tool's definition Dislike the current track (for recommendation training)
Attacks that exploit this kind of access
The rule that runs spotify_dislike_track 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_dislike_track, this is the rule to start with:
spotify_dislike_track stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_dislike_track call is checked against it from then on.
Questions about spotify_dislike_track
Dislike the current track (for recommendation training). It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for spotify_dislike_track: 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_dislike_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the spotify_dislike_track 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_dislike_track. 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_dislike_track 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.
This server
Across the catalogue