AI agents call get_now_playing to retrieve information from Sysprobe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of media playback (player type, status, artist, title) via MPRIS protocol. It is a purely informational read operation with no side effects, no command execution, no data modification, and no external effects. The low severity reflects minimal risk if misused by an AI agent.
From the tool's definition 'Current media: player, status, artist/title (MPRIS via playerctl)' — the tool retrieves current playback state from the media player interface without modifying, creating, or executing operations.
Attacks that exploit this kind of access
Current media: player, status, artist/title (MPRIS via playerctl). It is categorised as a Read tool in the Sysprobe MCP Server, which means it retrieves data without modifying state.
Register the Sysprobe MCP server in PolicyLayer and add a rule for get_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 Sysprobe. Nothing to install.
get_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 get_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 get_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.
get_now_playing is provided by the Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_now_playing is one line of Sysprobe's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →