playback_control

Control playback: play, pause, next, previous, shuffle, repeat, like, dislike

SERVERYtm SOURCE4shil/ytm-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/4shil-ytm-mcp/playback-control.md

WHAT IT DOES

What playback_control does on Ytm

AI agents invoke playback_control to trigger actions in Ytm. 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 playback_control is rated High

This tool triggers external operations on a media player (YouTube Music), controlling playback state and interactions. These are real-time actions with side effects on an external system. 'Like' and 'dislike' also modify user preference data on the platform. No data is destroyed or financial transactions are made, but it executes commands against an external service.

From the tool's definition Control playback: play, pause, next, previous, shuffle, repeat, like, dislike

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs playback_control safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ytm, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "playback_control": {
      "limits": [
        {
          "counter": "playback_control_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 Ytm, apply this rule, and every playback_control call is checked against it from then on.

FAQ

Questions about playback_control

What does the playback_control tool do? +

Control playback: play, pause, next, previous, shuffle, repeat, like, dislike. It is categorised as a Execute tool in the Ytm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on playback_control? +

Register the Ytm 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 Ytm. Nothing to install.

What risk level is playback_control? +

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

Can I rate-limit playback_control? +

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.

How do I block playback_control completely? +

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.

What MCP server provides playback_control? +

playback_control is provided by the Ytm MCP server (4shil/ytm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ytm, and thousands of servers like it.

This server

All 12 Ytm tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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