Generate a custom Spotify Wrapped summary for ANY time period. Unlike Spotify
AI agents call create_custom_wrapped to retrieve information from Your Spotify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool generates/reads a summary report of listening history data. It queries and aggregates existing data to produce analytics output, similar to analyze_listening_patterns. There is no indication it writes, modifies, or deletes any data. The description is truncated ('Unlike Spotify...') which slightly reduces confidence, but the core action is generating a summary report — a read/analytics operation.
From the tool's definition Generate a custom Spotify Wrapped summary for ANY time period
Attacks that exploit this kind of access
Generate a custom Spotify Wrapped summary for ANY time period. Unlike Spotify. It is categorised as a Read tool in the Your Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Your Spotify MCP Server MCP server in PolicyLayer and add a rule for create_custom_wrapped: 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 Your Spotify MCP Server. Nothing to install.
create_custom_wrapped is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the create_custom_wrapped 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 create_custom_wrapped. 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.
create_custom_wrapped is provided by the Your Spotify MCP Server MCP server (pentafive/your-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 →