Search through your complete Spotify listening history. Unlike Spotify
AI agents call search_listening_history 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 queries and retrieves listening history data with no side effects. It is a read-only operation that does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an agent could retrieve personal listening data, which is a privacy concern but not destructive, financial, or operationally dangerous.
From the tool's definition Tool name 'search_listening_history' and description 'Search through your complete Spotify listening history' indicate a query operation that retrieves data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Search through your complete Spotify listening history. 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 search_listening_history: 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.
search_listening_history 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 search_listening_history 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 search_listening_history. 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.
search_listening_history 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 →