google_videos
Search Google video results. Returns normalized Google video vertical results (title, platform, link, duration, age) parsed from the public Google video results page. Locale defaults to country=us and lang=en. Returns 503 when Google serves a challenge page or unusable HTML.
This record as markdown: /tools/crawlora-mcp/google-videos.md
What google_videos does on Crawlora
AI agents call google_videos 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 | Yes | Search query |
lang | string | — | Google UI language; defaults to en |
page | integer | — | 1-based page number; defaults to 1 |
count | integer | — | Results per page; defaults to 10, clamped to 1..50 |
country | string | — | Two-letter country code; defaults to us |
Parameters from the server's own tool schema.
Why google_videos is rated Low
The tool queries and returns publicly available Google video search results. It performs a read-only search operation that retrieves data without creating, modifying, deleting, or executing any operations. The severity is low because it only accesses public information with no blast radius for misuse beyond potential rate-limiting or terms-of-service violations.
From the tool's definition Tool description states it "Search[es] Google video results" and "Returns normalized Google video vertical results (title, platform, link, duration, age) parsed from the public Google video results page." These are retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs google_videos 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 google_videos, this is the rule to start with:
google_videos 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 google_videos call is checked against it from then on.
Questions about google_videos
Search Google video results. Returns normalized Google video vertical results (title, platform, link, duration, age) parsed from the public Google video results page. Locale defaults to country=us and lang=en. Returns 503 when Google serves a challenge page or unusable HTML. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
google_videos accepts 5 parameters: q, lang, page, count, country. Required: q. 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 google_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 Crawlora. Nothing to install.
google_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 google_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 google_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.
google_videos 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