AI agents call youtube_geography to retrieve information from Youtube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analytics querying on existing channel data. It retrieves geographical performance metrics but does not modify any data, execute code, delete content, or commit financial obligations. The blast radius of misuse is minimal — an agent could exfiltrate channel analytics, but cannot harm the channel itself or take irreversible actions. Classified as Read with low severity.
From the tool's definition Tool description states it 'Break down views, watch time, and average view duration by country' — these are read-only analytics queries that retrieve data without modification.
Attacks that exploit this kind of access
Break down views, watch time, and average view duration by country for the authenticated channel. Args: - \. It is categorised as a Read tool in the Youtube MCP Server, which means it retrieves data without modifying state.
Register the Youtube MCP server in PolicyLayer and add a rule for youtube_geography: 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.
youtube_geography is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the youtube_geography 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 youtube_geography. 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.
youtube_geography is provided by the Youtube MCP server (tuitamogamer-gpt/youtube-mcp-server). 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 →