spotify_get_track_uri

Get ONLY the Spotify URI of the currently playing track. Returns URI as text.

Server Spotify MCP Server llmtooling/spotify-mcp-server
Category Read
Risk class Low
Parameters 00 required

What spotify_get_track_uri does on Spotify MCP Server

AI agents call spotify_get_track_uri 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.

Why spotify_get_track_uri needs a policy

This is a straightforward data retrieval operation. It queries the current playback state to return a track identifier. There are no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an AI agent could only retrieve URIs it already has access to. Severity is low because URIs are non-sensitive identifiers widely used in Spotify integrations.

From the tool's definition Tool name 'spotify_get_track_uri' with description 'Get ONLY the Spotify URI of the currently playing track. Returns URI as text.' — explicitly retrieves data (URI identifier) with no modification, deletion, or execution of external operations.

Questions about spotify_get_track_uri

What does the spotify_get_track_uri tool do? +

Get ONLY the Spotify URI of the currently playing track. Returns URI as text. It is categorised as a Read tool in the Spotify MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spotify_get_track_uri? +

Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for spotify_get_track_uri: 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.

What risk level is spotify_get_track_uri? +

spotify_get_track_uri is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit spotify_get_track_uri? +

Yes. Add a rate_limit block to the spotify_get_track_uri 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.

How do I block spotify_get_track_uri completely? +

Set action: deny in the PolicyLayer policy for spotify_get_track_uri. 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.

What MCP server provides spotify_get_track_uri? +

spotify_get_track_uri 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.