This endpoint will provide you with estimated monthly traffic volumes for up to 1,000 domains, subdomains, or webpages. Along with organic search traffic estimations, you will also get separate values for paid search, featured snippet, and local pack results.
AI agents call dataforseo_labs_bulk_traffic_estimation 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 |
|---|---|---|---|
targets | array | Yes | target domains, subdomains, and webpages. you can specify domains, subdomains, and webpages in this field; domains and subdomains should be specified wi |
item_types | array | — | display results by item type indicates the type of search results included in the response |
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' |
ignore_synonyms | boolean | — | ignore highly similar keywords, if set to true, results will be more accurate |
Parameters from the server's own tool schema.
This is a pure data retrieval tool that queries traffic metrics for domains/subdomains/webpages. It returns estimates without side effects or state changes. The 'bulk' aspect (1,000 items) increases the information volume but not the risk category. No financial transactions, code execution, data modification, or destructive operations are involved.
From the tool's definition The tool 'will provide you with estimated monthly traffic volumes' and 'get separate values' — it retrieves and queries traffic estimation data from the DataForSEO API with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
This endpoint will provide you with estimated monthly traffic volumes for up to 1,000 domains, subdomains, or webpages. Along with organic search traffic estimations, you will also get separate values for paid search, featured snippet, and local pack results. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
dataforseo_labs_bulk_traffic_estimation accepts 5 parameters: targets, item_types, language_code, location_name, ignore_synonyms. Required: targets. 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_bulk_traffic_estimation: 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_bulk_traffic_estimation 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_bulk_traffic_estimation 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_bulk_traffic_estimation. 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_bulk_traffic_estimation 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.