google_trends_explore_interest_by_region
Google Trends interest by region. Returns only the interest-by-region widget from the Google Trends Explore widget flow. Supports multiple comparison terms and returns an empty interest_by_region array when Google returns no rows.
This record as markdown: /tools/crawlora-mcp/google-trends-explore-interest-by-region.md
What google_trends_explore_interest_by_region does on Crawlora
AI agents call google_trends_explore_interest_by_region 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 |
|---|---|---|---|
request | object | Yes | Explore request |
Parameters from the server's own tool schema.
Why google_trends_explore_interest_by_region is rated Low
Even though google_trends_explore_interest_by_region only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs google_trends_explore_interest_by_region 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_trends_explore_interest_by_region, this is the rule to start with:
google_trends_explore_interest_by_region 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_trends_explore_interest_by_region call is checked against it from then on.
Questions about google_trends_explore_interest_by_region
Google Trends interest by region. Returns only the interest-by-region widget from the Google Trends Explore widget flow. Supports multiple comparison terms and returns an empty interest_by_region array when Google returns no rows. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
google_trends_explore_interest_by_region accepts 1 parameter: request. Required: request. 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_trends_explore_interest_by_region: 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_trends_explore_interest_by_region 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_trends_explore_interest_by_region 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_trends_explore_interest_by_region. 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_trends_explore_interest_by_region 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