youtube_search
Search YouTube. Returns normalized YouTube search results using YouTube's InnerTube search API. Pass continuation_token from a previous response to retrieve the next page. Use q as the primary query parameter; search_query is accepted as an alias.
This record as markdown: /tools/crawlora-mcp/youtube-search.md
What youtube_search does on Crawlora
AI agents call youtube_search to retrieve information from Crawlora 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 |
|---|---|---|---|
q | string | — | Search query |
type | string | — | Filter by type |
params | string | — | Raw protobuf-encoded search filter (base64) |
sort_by | string | — | Sort results |
duration | string | — | Filter by duration |
features | string | — | Comma-separated feature filters |
upload_date | string | — | Filter by upload date |
search_query | string | — | Alias for q |
continuation_token | string | — | Pagination token returned by a previous request |
Parameters from the server's own tool schema.
Why youtube_search is rated Low
This tool retrieves and queries YouTube search data without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns search results. The low severity reflects minimal risk—search results are public data and misuse would have limited blast radius.
From the tool's definition Tool description explicitly states 'Search YouTube' and 'Returns normalized YouTube search results', indicating data retrieval with no modification or side effects.
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 Crawlora, 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 Crawlora, apply this rule, and every youtube_search call is checked against it from then on.
Questions about youtube_search
Search YouTube. Returns normalized YouTube search results using YouTube's InnerTube search API. Pass continuation_token from a previous response to retrieve the next page. Use q as the primary query parameter; search_query is accepted as an alias. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
youtube_search accepts 9 parameters: q, type, params, sort_by, duration, features, upload_date, search_query, continuation_token. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora 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 Crawlora. 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 Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue