Enable or disable shuffle mode for queue playback.
AI agents use sonos_set_shuffle 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 creates or modifies data reversibly—toggling shuffle mode changes the device's configuration state without deleting data or executing arbitrary code. While it affects audio playback behavior, the action is easily undone by toggling shuffle off again.
From the tool's definition The tool modifies playback state by enabling or disabling shuffle mode, which changes how the queue is presented during playback. This is a reversible state modification on the Sonos device.
Documented attack patterns abuse exactly the kind of access sonos_set_shuffle 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_set_shuffle:
{
"version": "1",
"default": "deny",
"tools": {
"sonos_set_shuffle": {
"limits": [
{
"counter": "sonos_set_shuffle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sonos_set_shuffle 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.
Enable or disable shuffle mode for queue playback. 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_set_shuffle: 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_set_shuffle 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_set_shuffle 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_set_shuffle. 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_set_shuffle 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.