list_device_presets

List stored device name labels and volume presets.

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/list-device-presets.md

WHAT IT DOES

What list_device_presets does on Spotify

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

Tool retrieves stored configuration data without modifying or executing actions.

From the tool's definition List stored device name labels and volume presets.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_device_presets Allowed

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

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

FAQ

Questions about list_device_presets

What does the list_device_presets tool do? +

List stored device name labels and volume presets. 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 list_device_presets? +

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

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

Can I rate-limit list_device_presets? +

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

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

list_device_presets 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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