bing_videos
Search Bing video results. Returns normalized Bing video search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Bing video HTML/async pages and return 503 when Bing serves a challenge page or unusable HTML.
This record as markdown: /tools/crawlora-mcp/bing-videos.md
What bing_videos does on Crawlora
AI agents call bing_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 | — | Bing UI language; defaults to en-us |
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 bing_videos is rated Low
This tool retrieves and returns video search results from a public search engine without modifying, creating, deleting, or executing any data or operations. It is purely a read/query operation with minimal risk profile. The only constraint noted is potential 503 errors from Bing's challenge pages, which does not elevate the risk category.
From the tool's definition Tool performs 'Search Bing video results' and 'Returns normalized Bing video search results for a query string' — these are query operations with no side effects.
Attacks that exploit this kind of access
The rule that runs bing_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 bing_videos, this is the rule to start with:
bing_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 bing_videos call is checked against it from then on.
Questions about bing_videos
Search Bing video results. Returns normalized Bing video search results for a query string. Locale defaults to country=us and lang=en-us. Results are fetched from public Bing video HTML/async pages and return 503 when Bing 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.
bing_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 bing_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.
bing_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 bing_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 bing_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.
bing_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