Medium Risk

sonos_save_queue

Save the current queue as a Sonos playlist with the specified title.

How to control sonos_save_queue ↓

What sonos_save_queue does on Sonos Ts

AI agents use sonos_save_queue to create or update resources in Sonos Ts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sonos Ts environment.

Medium Risk

Why sonos_save_queue needs a policy

This tool creates a new persistent Sonos playlist by saving the current queue. This is a write operation that modifies the user's playlist library by adding a new resource (the saved playlist). While reversible through deletion, it commits data to persistent storage.

From the tool's definition Save the current queue as a Sonos playlist with the specified title.

Documented attack patterns abuse exactly the kind of access sonos_save_queue gives an agent:

How to control sonos_save_queue

PolicyLayer is an MCP gateway — it sits between your AI agents and Sonos Ts, and nothing reaches the server without passing your rules. This is the rule we recommend for sonos_save_queue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sonos_save_queue": {
      "limits": [
        {
          "counter": "sonos_save_queue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

sonos_save_queue stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sonos Ts — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about sonos_save_queue

What does the sonos_save_queue tool do? +

Save the current queue as a Sonos playlist with the specified title. It is categorised as a Write tool in the Sonos Ts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sonos_save_queue? +

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

What risk level is sonos_save_queue? +

sonos_save_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sonos_save_queue? +

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

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

sonos_save_queue is provided by the Sonos Ts MCP server (tommertom/sonos-ts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sonos Ts tool call.

Start from Sonos Ts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

60 Sonos Ts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.