Mute or unmute a Sonos device. Mute preserves volume level for quick unmute.
AI agents use sonos_set_mute 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 device state (mute/unmute toggle) but does so reversibly without data loss or irreversible consequences. It affects only audio output behavior on a single device with no blast radius beyond local audio control. Severity is low because muting audio is a benign operation with trivial user impact and easily reversible by the user or system.
From the tool's definition Tool description states 'Mute or unmute a Sonos device', indicating state modification of audio device settings. The action is reversible (can unmute after muting) and preserves the underlying volume level, confirming Write rather than Destructive behavior.
Documented attack patterns abuse exactly the kind of access sonos_set_mute 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_mute:
{
"version": "1",
"default": "deny",
"tools": {
"sonos_set_mute": {
"limits": [
{
"counter": "sonos_set_mute_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} sonos_set_mute 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.
Mute or unmute a Sonos device. Mute preserves volume level for quick unmute. 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_mute: 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_mute 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_mute 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_mute. 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_mute 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.