Low Risk

youtube_getInfo

Get and save YouTube video information. Provide a YouTube video URL.

How to control youtube_getInfo ↓

What youtube_getInfo does on VidCap YouTube API MCP Server

AI agents call youtube_getInfo to retrieve information from VidCap YouTube API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why youtube_getInfo needs a policy

youtube_getInfo retrieves publicly available video metadata (title, description, duration, view count, etc.) with no side effects beyond caching/storing the retrieved data locally. This is a standard Read operation. While it says 'save', this refers to locally caching retrieved information, not modifying YouTube or user data. No destructive, financial, or execution risks are present.

From the tool's definition Tool description states 'Get and save YouTube video information' from a video URL. This is a retrieval operation that queries YouTube metadata.

Documented attack patterns abuse exactly the kind of access youtube_getInfo gives an agent:

How to control youtube_getInfo

PolicyLayer is an MCP gateway — it sits between your AI agents and VidCap YouTube API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for youtube_getInfo:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "youtube_getInfo": {}
  }
}

youtube_getInfo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register VidCap YouTube API MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about youtube_getInfo

What does the youtube_getInfo tool do? +

Get and save YouTube video information. Provide a YouTube video URL. It is categorised as a Read tool in the VidCap YouTube API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on youtube_getInfo? +

Register the VidCap YouTube API MCP Server MCP server in PolicyLayer and add a rule for youtube_getInfo: 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 VidCap YouTube API MCP Server. Nothing to install.

What risk level is youtube_getInfo? +

youtube_getInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit youtube_getInfo? +

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

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

youtube_getInfo is provided by the VidCap YouTube API MCP Server MCP server (mrgoonie/vidcap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VidCap YouTube API MCP Server tool call.

Start from VidCap YouTube API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

8 VidCap YouTube API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.