Follow one or more artists or users. Auto-chunks at 50 IDs per request.
AI agents use follow_artists_or_users to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.
Following artists or users is a reversible write action — it creates a follow relationship that can be undone (unfollowed). No data is deleted, no code is executed, and no financial transaction occurs. The blast radius is low since misuse would only result in unwanted follows, which are easily reversed.
From the tool's definition Follow one or more artists or users. Auto-chunks at 50 IDs per request.
Attacks that exploit this kind of access
Follow one or more artists or users. Auto-chunks at 50 IDs per request. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for follow_artists_or_users: 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 MCP Server. Nothing to install.
follow_artists_or_users 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 follow_artists_or_users 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 follow_artists_or_users. 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.
follow_artists_or_users is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →