artistwatch_new_additions

Watches your FOLLOWED artists for new material: walks /me/following, probes each artist\

SERVERSpotify SOURCE@novalux12/spotify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/artistwatch-new-additions.md

WHAT IT DOES

What artistwatch_new_additions does on Spotify

AI agents call artistwatch_new_additions to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why artistwatch_new_additions is rated Low

Tool reads followed artists and checks for new material without modifying data.

From the tool's definition Watches followed artists, walks /me/following, probes each artist

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs artistwatch_new_additions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For artistwatch_new_additions, this is the rule to start with:

artistwatch_new_additions Allowed

artistwatch_new_additions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "artistwatch_new_additions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every artistwatch_new_additions call is checked against it from then on.

FAQ

Questions about artistwatch_new_additions

What does the artistwatch_new_additions tool do? +

Watches your FOLLOWED artists for new material: walks /me/following, probes each artist\. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on artistwatch_new_additions? +

Register the Spotify MCP server in PolicyLayer and add a rule for artistwatch_new_additions: 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 Spotify. Nothing to install.

What risk level is artistwatch_new_additions? +

artistwatch_new_additions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit artistwatch_new_additions? +

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

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

artistwatch_new_additions is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →