spotify_add_track_to_library
Save the current track to liked songs
This record as markdown: /tools/mukul975-mcp-windows-automation/spotify-add-track-to-library.md
What spotify_add_track_to_library does on Mcp Windows
AI agents use spotify_add_track_to_library 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_add_track_to_library is rated Medium
This tool creates or modifies user data (liked songs library) in a reversible manner. It does not execute arbitrary commands, delete data, or create financial obligations. The operation is benign from a security perspective—adding a track to a library is a standard, user-initiated action with minimal blast radius.
From the tool's definition Tool name 'spotify_add_track_to_library' and description 'Save the current track to liked songs' indicate a write operation that adds/modifies user library data.
Attacks that exploit this kind of access
The rule that runs spotify_add_track_to_library 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_add_track_to_library, this is the rule to start with:
spotify_add_track_to_library 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_add_track_to_library call is checked against it from then on.
Questions about spotify_add_track_to_library
Save the current track to liked songs. 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_add_track_to_library: 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_add_track_to_library 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_add_track_to_library 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_add_track_to_library. 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_add_track_to_library 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