AI agents use add_to_playlist to create or update resources in Youtube — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Youtube environment.
This tool creates a new relationship (adds a video to a playlist) which is reversible—the video can be removed via delete operations. It modifies a playlist's contents without destroying data or executing arbitrary operations. The low severity reflects minimal blast radius: an AI agent misusing this tool would add unwanted videos to playlists, which is easily undone and has no financial or destructive impact.
From the tool's definition Tool name 'add_to_playlist' and description 'Add a video to a playlist' indicate a create/modify operation that adds content to an existing collection.
Attacks that exploit this kind of access
Add a video to a playlist. Costs 50 quota units. It is categorised as a Write tool in the Youtube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Youtube MCP server in PolicyLayer and add a rule for add_to_playlist: 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 Youtube. Nothing to install.
add_to_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_to_playlist 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 add_to_playlist. 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.
add_to_playlist is provided by the Youtube MCP server (kpfitzgerald/youtube-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 →