playback_control
Control Music playback: play, pause, nextTrack, previousTrack.
This record as markdown: /tools/io-github-heznpc-iconnect/playback-control.md
What playback_control does on Iconnect
AI agents invoke playback_control to trigger actions in Iconnect. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why playback_control is rated High
This tool triggers external operations on the Music app (play, pause, skip tracks), which are actions with real-world effects on a running application. It does not read or write data persistently, but executes commands against an external system. Severity is low as the blast radius of misuse is minimal — worst case, it disrupts music playback.
From the tool's definition Control Music playback: play, pause, nextTrack, previousTrack
Attacks that exploit this kind of access
The rule that runs playback_control safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For playback_control, this is the rule to start with:
playback_control stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every playback_control call is checked against it from then on.
Questions about playback_control
Control Music playback: play, pause, nextTrack, previousTrack. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for playback_control: 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 Iconnect. Nothing to install.
playback_control is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the playback_control 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 playback_control. 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.
playback_control is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue