play_track

Play a specific track by name, optionally from a specific playlist.

SERVERIconnect SOURCEiconnect-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/play-track.md

WHAT IT DOES

What play_track does on Iconnect

AI agents invoke play_track 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.

RISK

Why play_track is rated High

Playing a track is an external operation that controls media playback on the system. It doesn't read/write data persistently, isn't destructive or financial, but it executes an action (start playback) on an external application/device. Severity is low as misuse has minimal blast radius.

From the tool's definition 'Play a specific track by name' — triggers playback on the device, an external operation with real-world effect

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs play_track 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 play_track, this is the rule to start with:

play_track Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "play_track": {
      "limits": [
        {
          "counter": "play_track_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every play_track call is checked against it from then on.

FAQ

Questions about play_track

What does the play_track tool do? +

Play a specific track by name, optionally from a specific playlist. 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.

How do I enforce a policy on play_track? +

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

What risk level is play_track? +

play_track is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit play_track? +

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

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

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

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools → High-risk tools on this server →

Across the catalogue

music_play on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →