This endpoint will provide you with a list of subdomains of the specified domain, along with the ranking distribution across organic and paid search. In addition to that, you will also get the estimated traffic volume of subdomains based on search volume.
AI agents call dataforseo_labs_google_subdomains 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 |
|---|---|---|---|
limit | number | — | Maximum number of keywords to return |
offset | number | — | offset in the results array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in |
target | string | Yes | target domain |
filters | array | — | Array-based filter expression. A single condition is a 3-element array: [field, operator, value]. Combine conditions with ["and"|"or"] between them: [condition, |
order_by | array | — | results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorte |
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 |
include_clickstream_data | boolean | — | Include or exclude data from clickstream-based metrics in the result |
Parameters from the server's own tool schema.
This is a query endpoint that returns information about subdomains and their search performance metrics. There are no side effects, no data modification, and no code execution. The blast radius of misuse is minimal—an agent could only retrieve SEO intelligence data. Classification as Read is appropriate.
From the tool's definition The tool provides a list of subdomains, ranking distribution, and estimated traffic volume—all retrieved data with no modification, deletion, or execution of code. The description uses verbs like 'provide' and 'get', indicating data retrieval only.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
This endpoint will provide you with a list of subdomains of the specified domain, along with the ranking distribution across organic and paid search. In addition to that, you will also get the estimated traffic volume of subdomains based on search volume. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
dataforseo_labs_google_subdomains accepts 10 parameters: limit, offset, target, filters, order_by, item_types, language_code, location_name, ignore_synonyms, include_clickstream_data. Required: target. 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_subdomains: 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_subdomains 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_subdomains 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_subdomains. 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_subdomains 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.