google-trends.related_queries
Fetch Google Trends related queries for one to five keywords. Returns a JSON object whose top-level keys are your keywords. Each value has top and rising sections; each section has query (rank index to query string) and value (rank index to score). Requires start in datetime-with-timezone form (f...
This record as markdown: /tools/io-github-vee3io-vee3/google-trends.related-queries.md
What google-trends.related_queries does on Vee3
AI agents call google-trends.related_queries 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 |
|---|---|---|---|
end | object | — | Range end in datetime-with-timezone form. Defaults to now. |
gprop | object | — | Google property filter (for example images, news, youtube, froogle). Defaults to all. |
start | string | Yes | Range start in datetime-with-timezone form (for example 2020-05-01T00:43:37+0100). |
region | object | — | Region within country. Requires country when set. |
country | object | — | Country name for geo filtering. Defaults to global. |
category | object | — | Trends category or subcategory. Defaults to all. |
keywords | array | Yes | Up to five keywords to compare. |
Parameters from the server's own tool schema.
Why google-trends.related_queries is rated Low
This tool only retrieves/queries publicly available Google Trends data about related search queries. It has no side effects, does not modify any data, and cannot cause harm beyond exposing trending query information.
From the tool's definition Fetch Google Trends related queries for one to five keywords
Attacks that exploit this kind of access
The rule that runs google-trends.related_queries 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 google-trends.related_queries, this is the rule to start with:
google-trends.related_queries 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 google-trends.related_queries call is checked against it from then on.
Questions about google-trends.related_queries
Fetch Google Trends related queries for one to five keywords. Returns a JSON object whose top-level keys are your keywords. Each value has top and rising sections; each section has query (rank index to query string) and value (rank index to score). Requires start in datetime-with-timezone form (for example 2020-05-01T00:43:37+0100). Optional end defaults to now. country defaults to global; region requires a valid country. category and gprop default to all when omitted or empty. Use google-trends.categories and google-trends.regions to discover valid category, country, and region values. Cost = 40 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
google-trends.related_queries accepts 7 parameters: end, gprop, start, region, country, category, keywords. Required: start, keywords. 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 google-trends.related_queries: 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.
google-trends.related_queries 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.related_queries 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.related_queries. 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.related_queries 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