spotify_uri_stats

Summarise Spotify references by validity, form, or entity kind using the shared parser.

SERVERSpotify SOURCE@novalux12/spotify-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/spotify-uri-stats.md

WHAT IT DOES

What spotify_uri_stats does on Spotify

AI agents call spotify_uri_stats to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why spotify_uri_stats is rated Low

Tool analyzes and summarizes Spotify data without modifying or executing external operations.

From the tool's definition Summarise Spotify references by validity, form, or entity kind

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spotify_uri_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_uri_stats, this is the rule to start with:

spotify_uri_stats Allowed

spotify_uri_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spotify_uri_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every spotify_uri_stats call is checked against it from then on.

FAQ

Questions about spotify_uri_stats

What does the spotify_uri_stats tool do? +

Summarise Spotify references by validity, form, or entity kind using the shared parser. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on spotify_uri_stats? +

Register the Spotify MCP server in PolicyLayer and add a rule for spotify_uri_stats: 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. Nothing to install.

What risk level is spotify_uri_stats? +

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

Can I rate-limit spotify_uri_stats? +

Yes. Add a rate_limit block to the spotify_uri_stats 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_uri_stats completely? +

Set action: deny in the PolicyLayer policy for spotify_uri_stats. 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_uri_stats? +

spotify_uri_stats is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools →

Across the catalogue

cache_stats on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →