Low Risk

get_all_device_states

Retrieve the state information for all discovered Sonos devices.

How to control get_all_device_states ↓

What get_all_device_states does on Sonos MCP Server

AI agents call get_all_device_states 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_all_device_states needs a policy

This tool retrieves and queries state information from Sonos devices without modifying, executing operations, or causing irreversible changes. It is a passive read operation that returns device status, fitting the 'Read' category. Severity is low because the blast radius of misuse is minimal—an agent could only gather information about device states with no ability to control playback or make changes.

From the tool's definition Tool name 'get_all_device_states' and description 'Retrieve the state information for all discovered Sonos devices' indicate a query/retrieval operation with no side effects.

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

How to control get_all_device_states

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_all_device_states:

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

get_all_device_states 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_all_device_states

What does the get_all_device_states tool do? +

Retrieve the state information for all discovered Sonos devices. 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_all_device_states? +

Register the Sonos MCP Server MCP server in PolicyLayer and add a rule for get_all_device_states: 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_all_device_states? +

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

Can I rate-limit get_all_device_states? +

Yes. Add a rate_limit block to the get_all_device_states 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_all_device_states completely? +

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

get_all_device_states 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.