Get ONLY whether the current track is explicit. Returns
AI agents call spotify_get_track_explicit to retrieve information from 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 retrieves a single boolean property from the current track without modifying state or performing operations. It is a pure data retrieval operation, fitting squarely within the Read category. The low severity reflects minimal blast radius: an AI agent misusing this tool cannot cause harm beyond potentially accessing track metadata.
From the tool's definition spotify_get_track_explicit returns whether the current track is explicit — a metadata query with no side effects or modifications.
Attacks that exploit this kind of access
Get ONLY whether the current track is explicit. Returns. It is categorised as a Read tool in the Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for spotify_get_track_explicit: 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.
spotify_get_track_explicit 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_track_explicit 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_track_explicit. 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_track_explicit is provided by the Spotify MCP Server MCP server (llmtooling/spotify-mcp-server). 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 →