Low Risk

get_current_track_info

get_current_track_info

How to control get_current_track_info ↓

What get_current_track_info does on Sonos MCP Server

AI agents call get_current_track_info 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_current_track_info needs a policy

This tool retrieves information about the currently playing track on a Sonos device. It performs a read-only query with no ability to modify, delete, or execute operations. The empty description is compensated by the clear naming convention and server context showing this aligns with other Read operations like get_device_state and get_queue.

From the tool's definition Tool name 'get_current_track_info' indicates data retrieval. Server context describes 'retrieving device states' and 'now_playing' as sibling tools, establishing this as a query function with no side effects.

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

How to control get_current_track_info

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

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

get_current_track_info 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_current_track_info

What does the get_current_track_info tool do? +

get_current_track_info. 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_current_track_info? +

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

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

Can I rate-limit get_current_track_info? +

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

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

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