Get current playback settings including shuffle, repeat, crossfade, transport state, and speed.
AI agents call sonos_get_playback_state to retrieve information from Sonos Ts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns current playback configuration (shuffle, repeat, crossfade, transport state, speed). It performs no side effects, makes no changes to device state, and poses no risk of data loss, financial impact, or unintended actions. It is a pure information retrieval operation, fitting the 'Read' category with low severity.
From the tool's definition Tool name 'sonos_get_playback_state' and description 'Get current playback settings' indicate a query operation that retrieves information about audio device state without modifying or controlling anything.
Documented attack patterns abuse exactly the kind of access sonos_get_playback_state 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_get_playback_state:
{
"version": "1",
"default": "deny",
"tools": {
"sonos_get_playback_state": {}
}
}sonos_get_playback_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current playback settings including shuffle, repeat, crossfade, transport state, and speed. It is categorised as a Read tool in the Sonos Ts MCP Server, which means it retrieves data without modifying state.
Register the Sonos Ts MCP server in PolicyLayer and add a rule for sonos_get_playback_state: 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_get_playback_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sonos_get_playback_state 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_get_playback_state. 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_get_playback_state 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.