// SCAN REPORT

MCP YouTube Intelligence

10 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 11 Jun 2026

0 can modify or destroy data

10 read-only

10 tools total

Community server · catalogue entry verified 11/06/2026

How to control MCP YouTube Intelligence ↓

TOOL MAP

What MCP YouTube Intelligence exposes to your agents

Read (10) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control MCP YouTube Intelligence

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP YouTube Intelligence, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "extract_entities": {
    "limits": [
      {
        "counter": "extract_entities_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register MCP YouTube Intelligence — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP YOUTUBE INTELLIGENCE →

Free to start. No card required.

FULL CATALOGUE

All 10 MCP YouTube Intelligence tools

READ 10 tools

Read extract_entities Extract structured entities (companies, indices, people, sectors, etc.) from a video transcript. Read get_comments Get top comments for a video. Optionally summarize them. Read get_playlist Get playlist metadata and video list from a YouTube playlist. Read get_transcript Get video transcript. mode: Read get_video Get video metadata + summary (~300 tokens). Provide a YouTube video ID. Read monitor_channel Monitor a YouTube channel via RSS. action: Read search_transcripts Search stored transcripts by keyword. Returns matching snippets. Read search_youtube Search YouTube videos by keyword. Returns metadata list (~200 tokens). Read segment_topics Segment a video transcript into topics based on transition markers. Read generate_report Generate a structured markdown report for a YouTube video. Includes summary, topic segments, entities, and opt

FAQ

Questions about MCP YouTube Intelligence

Is the MCP YouTube Intelligence MCP server safe to use without restrictions? +

The MCP YouTube Intelligence server is primarily read-only with 10 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the MCP YouTube Intelligence MCP server expose? +

10 tools across 2 categories: Read, Write. 10 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on MCP YouTube Intelligence? +

Register the MCP YouTube Intelligence MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP YouTube Intelligence tool call.

Deterministic rules across all 10 MCP YouTube Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP YOUTUBE INTELLIGENCE →

Free to start. No card required.

10 MCP YouTube Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.