Here you will find all the necessary information about filters that can be used with DataForSEO WHOIS API endpoints. Please, keep in mind that filters are associated with a certain object in the result array, and should be specified accordingly.
AI agents call domain_analytics_whois_available_filters 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 |
|---|---|---|---|
tool | string | — | The name of the tool to get filters for |
Parameters from the server's own tool schema.
This is a metadata/documentation tool that retrieves filter specifications for API endpoints. It has no side effects, does not execute queries, create/modify/delete data, or move money. The blast radius of misuse is minimal—an agent could only retrieve filter documentation. Classified as Read with low severity.
From the tool's definition Tool provides information about available filters for WHOIS API endpoints. The verb "find" and "information about" indicate data retrieval.
Attacks that exploit this kind of access
Here you will find all the necessary information about filters that can be used with DataForSEO WHOIS API endpoints. Please, keep in mind that filters are associated with a certain object in the result array, and should be specified accordingly. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
domain_analytics_whois_available_filters accepts 1 parameter: tool. 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 domain_analytics_whois_available_filters: 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.
domain_analytics_whois_available_filters 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 domain_analytics_whois_available_filters 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 domain_analytics_whois_available_filters. 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.
domain_analytics_whois_available_filters 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.