taste_genre_bridge

Genre-bridge playlist spec: picks spanning two genres with evidence + risk per pick. Read-only, no auth.

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/taste-genre-bridge.md

WHAT IT DOES

What taste_genre_bridge does on Spotify

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

Tool retrieves and analyzes playlist recommendations without modifying data or executing actions.

From the tool's definition picks spanning two genres, read-only, no auth

Attacks that exploit this kind of access

RECOMMENDED RULE

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

taste_genre_bridge Allowed

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

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

FAQ

Questions about taste_genre_bridge

What does the taste_genre_bridge tool do? +

Genre-bridge playlist spec: picks spanning two genres with evidence + risk per pick. Read-only, no auth. 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 taste_genre_bridge? +

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

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

Can I rate-limit taste_genre_bridge? +

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

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

taste_genre_bridge 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 →