google-search.url_traffic_insights
Get Google keyword traffic insights and related keyword suggestions for a URL. Returns an array of keyword suggestions. Each item includes text, monthly search volume, competition_level, competition_index, low_bid, high_bid, and trend. Required: url and language (for example en). Optional: locati...
This record as markdown: /tools/io-github-vee3io-vee3/google-search.url-traffic-insights.md
What google-search.url_traffic_insights does on Vee3
AI agents call google-search.url_traffic_insights 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 |
|---|---|---|---|
url | string | Yes | Public http or https URL to get traffic insights and suggestions for. |
intent | object | — | Filter by search intent: informational, navigational, commercial, or transactional. |
language | string | Yes | Language code for the search market (for example en). |
location | object | — | Optional country or region code for localized traffic (for example US). Omit for global URL keyword insights. |
min_search_volume | integer | — | Minimum monthly search volume; only keywords at or above this threshold are returned. |
Parameters from the server's own tool schema.
Why google-search.url_traffic_insights is rated Low
This tool retrieves and queries publicly available SEO and keyword data from Google without creating, modifying, deleting, or executing anything. It is purely informational—a read operation with minimal blast radius even if misused by an agent (worst case: querying many URLs or unusual locations, which would waste tokens but cause no data loss or external side effects).
From the tool's definition Tool description states it 'Get[s] Google keyword traffic insights and related keyword suggestions for a URL' and 'Returns an array of keyword suggestions' with traffic metrics.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs google-search.url_traffic_insights 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-search.url_traffic_insights, this is the rule to start with:
google-search.url_traffic_insights 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-search.url_traffic_insights call is checked against it from then on.
Questions about google-search.url_traffic_insights
Get Google keyword traffic insights and related keyword suggestions for a URL. Returns an array of keyword suggestions. Each item includes text, monthly search volume, competition_level, competition_index, low_bid, high_bid, and trend. Required: url and language (for example en). Optional: location (for example US) for country-specific data; omit location for global results (default). Optional: min_search_volume (default 0) and intent (informational, navigational, commercial, or transactional). Cost = 20 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
google-search.url_traffic_insights accepts 5 parameters: url, intent, language, location, min_search_volume. Required: url, language. 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-search.url_traffic_insights: 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-search.url_traffic_insights 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-search.url_traffic_insights 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-search.url_traffic_insights. 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-search.url_traffic_insights 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