sonos_restore_snapshot

THE RISK

Medium Risk

Why sonos_restore_snapshot needs a policy

This tool modifies the audio device's current state (playback, volume, queue) by applying a saved snapshot. While the changes are technically reversible (another snapshot could be created and restored), the operation itself overwrites the current device state with stored configuration data.

From the tool's definition Tool description states 'Restore a previously saved snapshot to return device to its captured state' which modifies device state by restoring audio playback settings, volume levels, and queue configuration to a prior snapshot state.

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

POLICY

How to control sonos_restore_snapshot

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sonos_restore_snapshot": {
      "limits": [
        {
          "counter": "sonos_restore_snapshot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

sonos_restore_snapshot stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Sonos Ts — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sonos Ts tools

Destructive sonos_clear_queue Remove all tracks from the queue. Does not stop current playback. Destructive sonos_delete_alarm Delete an existing alarm permanently. Destructive sonos_remove_from_queue Remove a track from the queue at the specified position. Execute sonos_play Start or resume playback on a Sonos device. Continues from current queue position and resp Execute sonos_play_from_queue Start playing from the queue at a specific position. Execute sonos_previous Skip to previous track or restart current track if played more than a few seconds. Execute sonos_stop Stop playback on a Sonos device. Clears playback state, unlike pause which maintains posit Execute sonos_agent An AI-powered assistant that can take natural language instructions and autonomously contr

All 60 Sonos Ts tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sonos_restore_snapshot

What does the sonos_restore_snapshot tool do? +

Restore a previously saved snapshot to return device to its captured state. Optionally fade in volume. It is categorised as a Write tool in the Sonos Ts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sonos_restore_snapshot? +

Register the Sonos Ts MCP server in PolicyLayer and add a rule for sonos_restore_snapshot: 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.

What risk level is sonos_restore_snapshot? +

sonos_restore_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sonos_restore_snapshot? +

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

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

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

Enforce policy on every Sonos Ts tool call.

Start from Sonos Ts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →