expand_mood_to_queries

Turn a free-text listening mood into search terms (genres, keywords, terms to avoid) for search.

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/expand-mood-to-queries.md

WHAT IT DOES

What expand_mood_to_queries does on Spotify

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

Converts user mood input to search queries without modifying data or executing operations.

From the tool's definition Turn a free-text listening mood into search terms for search.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

expand_mood_to_queries Allowed

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

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

FAQ

Questions about expand_mood_to_queries

What does the expand_mood_to_queries tool do? +

Turn a free-text listening mood into search terms (genres, keywords, terms to avoid) for search. 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 expand_mood_to_queries? +

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

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

Can I rate-limit expand_mood_to_queries? +

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

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

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