Add a track URI to the playback queue. Supports music library URIs and streaming service URIs. Optional metadata in DIDL-Lite XML format.
AI agents use sonos_add_to_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.
This tool modifies the playback queue by adding tracks, which is a Write operation—data is created/appended reversibly. An agent could misuse it by flooding the queue with unwanted tracks, but this causes minimal harm (queue can be cleared) and no financial, destructive, or code-execution impact. Severity is low due to limited blast radius and easy remediation.
From the tool's definition Tool description states 'Add a track URI to the playback queue', which is a reversible modification operation. The action creates or appends data to the queue without permanent deletion or irreversible changes.
Documented attack patterns abuse exactly the kind of access sonos_add_to_queue gives an agent:
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_add_to_queue:
{
"version": "1",
"default": "deny",
"tools": {
"sonos_add_to_queue": {
"limits": [
{
"counter": "sonos_add_to_queue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sonos_add_to_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.
Free to start. No card required.
Add a track URI to the playback queue. Supports music library URIs and streaming service URIs. Optional metadata in DIDL-Lite XML format. 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.
Register the Sonos Ts MCP server in PolicyLayer and add a rule for sonos_add_to_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.
sonos_add_to_queue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sonos_add_to_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.
Set action: deny in the PolicyLayer policy for sonos_add_to_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.
sonos_add_to_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.
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.