Low Risk

get_queue

Retrieve the queue of tracks for a Sonos device.

How to control get_queue ↓

What get_queue does on Sonos MCP Server

AI agents call get_queue to retrieve information from Sonos MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_queue needs a policy

This tool only retrieves information about the track queue on a Sonos device. It performs no side effects, creates no data, executes no commands, and cannot delete or modify anything. It is a straightforward data retrieval operation, making it a Read category risk with low severity since queue information is non-sensitive device state data.

From the tool's definition Tool name 'get_queue' and description 'Retrieve the queue of tracks for a Sonos device' indicate a read-only query operation that returns data about the current playback queue without modifying any state.

Documented attack patterns abuse exactly the kind of access get_queue gives an agent:

How to control get_queue

PolicyLayer is an MCP gateway — it sits between your AI agents and Sonos MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_queue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_queue": {}
  }
}

get_queue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sonos MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_queue

What does the get_queue tool do? +

Retrieve the queue of tracks for a Sonos device. It is categorised as a Read tool in the Sonos MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_queue? +

Register the Sonos MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.

What risk level is get_queue? +

get_queue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_queue? +

Yes. Add a rate_limit block to the 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.

How do I block get_queue completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides get_queue? +

get_queue is provided by the Sonos MCP Server MCP server (winstonfassett/sonos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sonos MCP Server tool call.

Start from Sonos MCP Server, 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.

18 Sonos MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.