// SCAN REPORT

Youtube

36 tools. 13 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 5 Apr 2026

13 can modify or destroy data

23 read-only

36 tools total

// TOOL MAP

Read (23) Write / Execute (9) Destructive / Financial (4)

// WHAT CAN GO WRONG

Destructive tools (youtube_delete_comment, youtube_delete_playlist, youtube_rate_video) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (youtube_add_playlist_item, youtube_create_playlist, youtube_post_comment) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

One command. Full control.

Intercept sits between your agent and Youtube. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @youtube-mcp-server

Scans every tool. Generates a policy. Starts enforcing.

Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client

// RECOMMENDED RULES

Deny destructive operations

youtube_delete_comment:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

youtube_add_playlist_item:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

youtube_get_channel:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 36 YOUTUBE TOOLS

DESTRUCTIVE 4 tools

Destructive youtube_delete_comment Destructive youtube_delete_playlist Destructive youtube_rate_video Destructive youtube_remove_playlist_item

WRITE 9 tools

Write youtube_add_playlist_item Write youtube_create_playlist Write youtube_post_comment Write youtube_reply_comment Write youtube_update_comment Write youtube_update_playlist Write YOUTUBE_UPDATE_THUMBNAIL Write YOUTUBE_UPDATE_VIDEO Write YOUTUBE_UPLOAD_VIDEO

// FAQ

Can an AI agent delete data through the Youtube MCP server? +

Yes. The Youtube server exposes 4 destructive tools including youtube_delete_comment, youtube_delete_playlist, youtube_rate_video. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Youtube? +

The Youtube server has 9 write tools including youtube_add_playlist_item, youtube_create_playlist, youtube_post_comment. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Youtube MCP server expose? +

36 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 13 can modify, create, or delete data.

How do I add Intercept to my Youtube setup? +

One line change. Instead of running the Youtube server directly, prefix it with Intercept: intercept -c youtube.yaml -- npx -y @youtube-mcp-server. Download a pre-built policy from policylayer.com/policies/youtube and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init

Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.

Youtube

One command. Full control.

Other MCP servers with similar tools.

Control every MCP tool call your agent makes.

Control every MCP tool call
your agent makes.