Low Risk

get_device_state

get_device_state

How to control get_device_state ↓

What get_device_state does on Sonos MCP Server

AI agents call get_device_state 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_device_state needs a policy

This tool retrieves the current state of a Sonos device (e.g., playing/paused, volume, current track), producing no side effects or modifications. It is a read operation with minimal security risk. Tool description is empty, but context and naming pattern strongly indicate a query-only function. Confidence is high due to clear naming and server context.

From the tool's definition Tool name 'get_device_state' indicates state retrieval. Server description lists 'retrieving device states' as a core functionality.

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

How to control get_device_state

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

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

get_device_state 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_device_state

What does the get_device_state tool do? +

get_device_state. 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_device_state? +

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

What risk level is get_device_state? +

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

Can I rate-limit get_device_state? +

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

How do I block get_device_state completely? +

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

What MCP server provides get_device_state? +

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