Fetch AI Overviews brand names (v1/domain/aio/discover-brand)
AI agents call domainAioDiscoverBrand 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 retrieves SEO data (brand names) from the SE Ranking API without creating, modifying, deleting, or executing operations. It is a straightforward query operation that poses minimal security risk as it only reads publicly available or authorized SEO intelligence data.
From the tool's definition The tool 'domainAioDiscoverBrand' fetches brand names via an API endpoint (v1/domain/aio/discover-brand). The verb 'Fetch' and the read-only nature of querying AI Overviews brand data indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetch AI Overviews brand names (v1/domain/aio/discover-brand). 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 domainAioDiscoverBrand: 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.
domainAioDiscoverBrand 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 domainAioDiscoverBrand 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 domainAioDiscoverBrand. 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.
domainAioDiscoverBrand 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 →