AI agents call now_playing to retrieve information from Roon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries current playback information (track and state) without modifying, executing, or destructively affecting any data or system state. It is a passive information retrieval operation typical of Read category tools.
From the tool's definition Tool name 'now_playing' and description 'Get the currently playing track and state on a zone' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the currently playing track and state on a zone. It is categorised as a Read tool in the Roon MCP Server, which means it retrieves data without modifying state.
Register the Roon MCP server in PolicyLayer and add a rule for now_playing: 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 Roon. Nothing to install.
now_playing is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the now_playing 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.
Set action: deny in the PolicyLayer policy for now_playing. 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.
now_playing is provided by the Roon MCP server (txagscott/roon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →