Retrieve the current playback queue with track information. Supports pagination for large queues.
AI agents call sonos_get_queue 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 queries and returns information about the current playback queue state. It has no side effects—it does not modify, delete, or execute any operations on the Sonos device. Pagination support further confirms this is a standard read operation. The information retrieved (queue contents) is not sensitive financial data or system credentials, making this low severity even if misused by an AI agent.
From the tool's definition Tool description: 'Retrieve the current playback queue with track information.' The verb 'retrieve' and the read-only nature of obtaining queue state without modification indicate this is a data retrieval operation.
Documented attack patterns abuse exactly the kind of access sonos_get_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_get_queue:
{
"version": "1",
"default": "deny",
"tools": {
"sonos_get_queue": {}
}
}sonos_get_queue 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.
Retrieve the current playback queue with track information. Supports pagination for large queues. 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_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_get_queue 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_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_get_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_get_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.