library_growth_timeline
Show how fast your saved-track library grew: adds per month, busiest month, and your longest/current monthly add streaks. Read-only.
This record as markdown: /tools/novalux12-spotify-mcp/library-growth-timeline.md
What library_growth_timeline does on Spotify
AI agents use library_growth_timeline to create or update resources in Spotify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify environment.
Why library_growth_timeline is rated Medium
An AI agent can call library_growth_timeline faster than any human can review: one bad instruction and it creates or modifies resources in Spotify by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs library_growth_timeline 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 library_growth_timeline, this is the rule to start with:
library_growth_timeline 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 Spotify, apply this rule, and every library_growth_timeline call is checked against it from then on.
Questions about library_growth_timeline
Show how fast your saved-track library grew: adds per month, busiest month, and your longest/current monthly add streaks. Read-only. It is categorised as a Write tool in the Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP server in PolicyLayer and add a rule for library_growth_timeline: 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.
library_growth_timeline 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 library_growth_timeline 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 library_growth_timeline. 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.
library_growth_timeline 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.
More on Spotify, and thousands of servers like it.
This server
Across the catalogue