spotify_doctor

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-doctor.md

WHAT IT DOES

What spotify_doctor does on Spotify

AI agents call spotify_doctor 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_doctor is rated Low

Tool only reads diagnostics and account info; explicitly no mutations issued.

From the tool's definition read-only diagnostics... only live request is GET /me; no mutation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs spotify_doctor 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_doctor, this is the rule to start with:

spotify_doctor Allowed

spotify_doctor 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_doctor": {}
  }
}

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_doctor call is checked against it from then on.

FAQ

Questions about spotify_doctor

What does the spotify_doctor tool do? +

Run read-only diagnostics: token presence/expiry, auth-time scopes vs write tools enabled by active toolsets, Premium gating, rate-limit cooldown, config state, visible account details when reachable, and the live registered-tool surface with toolset/scope/READONLY trim causes. The only live request is GET /me; no mutation requests are issued. 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_doctor? +

Register the Spotify MCP server in PolicyLayer and add a rule for spotify_doctor: 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_doctor? +

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

Can I rate-limit spotify_doctor? +

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

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

spotify_doctor 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

The MCP Attack Database →

Guides

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