This endpoint will provide you with Google SERPs collected within the specified time frame. You will also receive a complete overview of featured snippets and other extra elements that were present within the specified dates. The data will allow you to analyze the dynamics of keyword rankings ove...
AI agents call dataforseo_labs_google_historical_serps 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 |
|---|---|---|---|
date_to | string | — | ending date of the time range, date format: YYYY-MM-DD |
keyword | string | Yes | target keyword |
date_from | string | — | starting date of the time range, date format: YYYY-MM-DD |
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 pure data retrieval tool that queries historical SERP (Search Engine Results Page) data from the DataForSEO API. It has no side effects, does not execute code or commands, does not modify data, and does not perform financial transactions. The blast radius of misuse is minimal—an agent could request excessive historical data or scrape competitive intelligence, but this is typical for Read operations.
From the tool's definition The tool 'will provide you with Google SERPs' and 'allows you to analyze the dynamics of keyword rankings over time' — it retrieves historical search engine results data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
This endpoint will provide you with Google SERPs collected within the specified time frame. You will also receive a complete overview of featured snippets and other extra elements that were present within the specified dates. The data will allow you to analyze the dynamics of keyword rankings over time for the specified keyword and location. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
dataforseo_labs_google_historical_serps accepts 5 parameters: date_to, keyword, date_from, language_code, location_name. Required: keyword. 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_serps: 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_serps 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_serps 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_serps. 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_serps 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.