AI agents call search_youtube_videos to retrieve information from PersonalizationMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries YouTube video data based on a search query. It does not create, modify, delete, or execute any operations—it only fetches information. While the server accesses personal data, this specific tool performs a standard search/query operation typical of Read-category tools. The blast radius of misuse is limited to information disclosure of publicly or user-accessible video content.
From the tool's definition Tool name 'search_youtube_videos' and description 'Search YouTube videos by query' indicate a retrieval operation with no side effects. The verb 'search' and function of querying video data are characteristic of Read category operations.
Documented attack patterns abuse exactly the kind of access search_youtube_videos gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PersonalizationMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_youtube_videos:
{
"version": "1",
"default": "deny",
"tools": {
"search_youtube_videos": {}
}
} search_youtube_videos is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search YouTube videos by query. It is categorised as a Read tool in the PersonalizationMCP MCP Server, which means it retrieves data without modifying state.
Register the Personalization MCP server in PolicyLayer and add a rule for search_youtube_videos: 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 PersonalizationMCP. Nothing to install.
search_youtube_videos 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 search_youtube_videos 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 search_youtube_videos. 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.
search_youtube_videos is provided by the Personalization MCP server (yangliangwei/personalizationmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 PersonalizationMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 PersonalizationMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.