Fetch AI Overviews domain keywords by target (v1/domain/aio/keywords-by-target)
AI agents call domainAioKeywordsByTarget to retrieve information from Seo Data Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns keyword performance data for SEO analysis purposes. It has no side effects—it does not create, modify, delete, or execute external commands. The data returned is read-only competitive/performance intelligence, typical of analytics platforms.
From the tool's definition Tool name and description indicate it 'Fetch[es]' keyword data 'by target' from an SEO analytics API. The verb 'fetch' combined with the endpoint structure (v1/domain/aio/keywords-by-target) and server context (SE Ranking data provider) confirms this…
Attacks that exploit this kind of access
Fetch AI Overviews domain keywords by target (v1/domain/aio/keywords-by-target). It is categorised as a Read tool in the Seo Data Api MCP Server, which means it retrieves data without modifying state.
Register the Seo Data Api MCP server in PolicyLayer and add a rule for domainAioKeywordsByTarget: 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 Seo Data Api. Nothing to install.
domainAioKeywordsByTarget 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 domainAioKeywordsByTarget 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 domainAioKeywordsByTarget. 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.
domainAioKeywordsByTarget is provided by the Seo Data Api MCP server (teake1404/seo-data-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →