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.
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.
Documented attack patterns abuse exactly the kind of access spotify_add_track_to_library 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 spotify_add_track_to_library:
{
"version": "1",
"default": "deny",
"tools": {
"spotify_add_track_to_library": {
"limits": [
{
"counter": "spotify_add_track_to_library_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.