google_trends_trending
Google Trends trending now data. Returns normalized Google Trends Trending Now rows from the internal TrendsUi batch RPC replay.
This record as markdown: /tools/crawlora-mcp/google-trends-trending.md
What google_trends_trending does on Crawlora
AI agents call google_trends_trending 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 |
|---|---|---|---|
hl | string | — | Google Trends UI locale |
tz | integer | — | Timezone offset minutes |
geo | string | — | Country/territory location code |
limit | integer | — | Maximum rows to return |
status | string | — | Trend status filter |
window | string | — | Trend window |
sort_by | string | — | Sort mode |
category | integer | — | Trending category id |
time_range | string | — | Alias for window |
Parameters from the server's own tool schema.
Why google_trends_trending is rated Low
Even though google_trends_trending 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_trending 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_trending, this is the rule to start with:
google_trends_trending 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_trending call is checked against it from then on.
Questions about google_trends_trending
Google Trends trending now data. Returns normalized Google Trends Trending Now rows from the internal TrendsUi batch RPC replay. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
google_trends_trending accepts 9 parameters: hl, tz, geo, limit, status, window, sort_by, category, time_range. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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