youtube.search_autocomplete
Get YouTube search autocomplete suggestions for a partial query. Returns the normalized query and an array of suggested search phrases. Optional language and location codes localize suggestions (defaults: en, US). Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/youtube.search-autocomplete.md
What youtube.search_autocomplete does on Vee3
AI agents call youtube.search_autocomplete to retrieve information from Vee3 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 |
|---|---|---|---|
query | string | Yes | Partial search keywords or phrase. |
language | string | — | Language code for localized suggestions (for example en). |
location | string | — | Country code for localized suggestions (for example US). |
Parameters from the server's own tool schema.
Why youtube.search_autocomplete is rated Low
This tool queries YouTube's autocomplete API to retrieve search suggestions. It has no side effects: it does not create, modify, delete, or execute anything. The optional localization parameters (language and location codes) are input filters for the read operation, not actions that alter state. This is a straightforward data retrieval function with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'Get YouTube search autocomplete suggestions' — a retrieval operation that returns 'normalized query and an array of suggested search phrases' with no mention of data modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs youtube.search_autocomplete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube.search_autocomplete, this is the rule to start with:
youtube.search_autocomplete 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 Vee3, apply this rule, and every youtube.search_autocomplete call is checked against it from then on.
Questions about youtube.search_autocomplete
Get YouTube search autocomplete suggestions for a partial query. Returns the normalized query and an array of suggested search phrases. Optional language and location codes localize suggestions (defaults: en, US). Cost = 8 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
youtube.search_autocomplete accepts 3 parameters: query, language, location. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for youtube.search_autocomplete: 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 Vee3. Nothing to install.
youtube.search_autocomplete 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_autocomplete 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_autocomplete. 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_autocomplete is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue