google-search.keyword_traffic_insights

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Low RISK CLASS

Category Read

Parameters 62 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/google-search.keyword-traffic-insights.md

WHAT IT DOES

What google-search.keyword_traffic_insights does on Vee3

AI agents call google-search.keyword_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
`mode`	string	—	Keyword suggestion filter: exact returns only suggestions that exactly match the seed keyword; all returns all suggestions (default).
`intent`	object	—	Filter by search intent: informational, navigational, commercial, or transactional.
`keyword`	string	Yes	Seed keyword to get traffic insights and suggestions for.
`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 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.

RISK

Why google-search.keyword_traffic_insights is rated Low

This is a straightforward data retrieval tool that queries Google's keyword analytics to provide SEO research insights. It has no side effects, does not create or modify data, does not execute code or commands, and does not involve financial transactions. The optional parameters (keyword, language, location, mode, filters, intent) are all read-only query filters.

From the tool's definition Tool retrieves keyword traffic data and suggestions including search volume, competition metrics, and trends.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google-search.keyword_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.keyword_traffic_insights, this is the rule to start with:

google-search.keyword_traffic_insights Allowed

google-search.keyword_traffic_insights is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google-search.keyword_traffic_insights": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-search.keyword_traffic_insights call is checked against it from then on.

FAQ

Questions about google-search.keyword_traffic_insights

What does the google-search.keyword_traffic_insights tool do? +

Get Google keyword traffic insights and related keyword suggestions for a seed keyword. Returns an array of keyword suggestions. Each item includes text, monthly search volume, competition_level, competition_index, low_bid, high_bid, and trend. Required: keyword and language (for example en). Optional: location (for example US) for country-specific data; omit location for global results (default). Optional: mode (exact or all, default all), 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.

What parameters does google-search.keyword_traffic_insights accept? +

google-search.keyword_traffic_insights accepts 6 parameters: mode, intent, keyword, language, location, min_search_volume. Required: keyword, language. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on google-search.keyword_traffic_insights? +

Register the Vee3 MCP server in PolicyLayer and add a rule for google-search.keyword_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.

What risk level is google-search.keyword_traffic_insights? +

google-search.keyword_traffic_insights is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google-search.keyword_traffic_insights? +

Yes. Add a rate_limit block to the google-search.keyword_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.

How do I block google-search.keyword_traffic_insights completely? +

Set action: deny in the PolicyLayer policy for google-search.keyword_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.

What MCP server provides google-search.keyword_traffic_insights? +

google-search.keyword_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.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 249 Vee3 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →