This endpoint provides Google historical keyword data for specified keywords, including search volume, cost-per-click, competition values for paid search, monthly searches, and search volume trends. You can get historical keyword data since August, 2021, depending on keywords along with location ...
AI agents call dataforseo_labs_google_historical_keyword_data to retrieve information from Dataforseo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
keywords | array | Yes | keywords required field The maximum number of keywords you can specify: 700 The maximum number of characters for each keyword: 80 The maximum number of words fo |
language_code | string | — | language code required field example: en |
location_name | string | — | full name of the location required field only in format "Country" (not "City" or "Region") example: 'United Kingdom', 'United States', 'Canada' |
Parameters from the server's own tool schema.
This is a straightforward data retrieval endpoint from a third-party SEO API. It queries historical metrics without any side effects, modifications, or ability to execute code or commands. The blast radius of misuse is minimal — worst case, an agent makes many queries consuming quota or scraping data, but no data is altered, deleted, or financial transactions occur.
From the tool's definition Tool provides historical keyword data retrieval (search volume, CPC, competition values, monthly searches, trends) with no modification, deletion, or execution capabilities. Description explicitly states 'provides' and 'get' — purely informational queries.
Attacks that exploit this kind of access
This endpoint provides Google historical keyword data for specified keywords, including search volume, cost-per-click, competition values for paid search, monthly searches, and search volume trends. You can get historical keyword data since August, 2021, depending on keywords along with location and language combination. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
dataforseo_labs_google_historical_keyword_data accepts 3 parameters: keywords, language_code, location_name. Required: keywords. The full parameter table on this page comes from the server's own tool schema.
Register the Dataforseo MCP server in PolicyLayer and add a rule for dataforseo_labs_google_historical_keyword_data: 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 Dataforseo. Nothing to install.
dataforseo_labs_google_historical_keyword_data 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 dataforseo_labs_google_historical_keyword_data 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 dataforseo_labs_google_historical_keyword_data. 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.
dataforseo_labs_google_historical_keyword_data is provided by the Dataforseo MCP server (dataforseo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.