spotify_get_audio_features
AI agents call spotify_get_audio_features to retrieve information from Spotify Playlist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves audio feature metadata for tracks (likely tempo, energy, danceability, acousticness, etc.) without modifying or deleting any data. It is a query/fetch operation with no side effects. Although the tool description is empty, the name and server context strongly indicate a Read classification.
From the tool's definition Tool name 'spotify_get_audio_features' indicates retrieval of audio feature data. Server description mentions 'finding similar tracks based on audio features' as a read operation.
Attacks that exploit this kind of access
spotify_get_audio_features. It is categorised as a Read tool in the Spotify Playlist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spotify Playlist MCP Server MCP server in PolicyLayer and add a rule for spotify_get_audio_features: 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 Playlist MCP Server. Nothing to install.
spotify_get_audio_features 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 spotify_get_audio_features 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 spotify_get_audio_features. 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.
spotify_get_audio_features is provided by the Spotify Playlist MCP Server MCP server (kylestratis/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 →