youtube_search
Search YouTube for videos, channels, or playlists.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/youtube-search.md
What youtube_search does on UnClick
AI agents call youtube_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | video, channel, or playlist (default: video) |
order | string | — | relevance, date, rating, viewCount, title |
query | string | Yes | |
api_key | string | Yes | |
channel_id | string | — | |
page_token | string | — | |
max_results | number | — | |
region_code | string | — | |
published_after | string | — | RFC 3339 datetime, e.g. 2024-01-01T00:00:00Z |
Parameters from the server's own tool schema.
Why youtube_search is rated Low
This tool performs a search query against YouTube's public content index, returning results without creating, modifying, deleting, or executing any operations. It is a straightforward read-only retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'youtube_search' and description 'Search YouTube for videos, channels, or playlists' indicate a retrieval operation with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs youtube_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_search, this is the rule to start with:
youtube_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every youtube_search call is checked against it from then on.
Questions about youtube_search
Search YouTube for videos, channels, or playlists. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
youtube_search accepts 9 parameters: type, order, query, api_key, channel_id, page_token, max_results, region_code, published_after. Required: query, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for youtube_search: 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 UnClick. Nothing to install.
youtube_search 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_search 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_search. 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_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue