Analyze branded vs non-branded search queries. Shows what percentage of traffic comes from brand searches.
AI agents call analyze_brand_queries to retrieve information from Google Search Console without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries analytics data from Google Search Console to provide insights on search traffic composition. It has no side effects, does not execute code or commands, does not modify data, and does not delete or create resources.
From the tool's definition Tool analyzes and shows search query data (branded vs non-branded traffic percentages) from Google Search Console without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Analyze branded vs non-branded search queries. Shows what percentage of traffic comes from brand searches. It is categorised as a Read tool in the Google Search Console MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console MCP server in PolicyLayer and add a rule for analyze_brand_queries: 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 Google Search Console. Nothing to install.
analyze_brand_queries 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 analyze_brand_queries 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 analyze_brand_queries. 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.
analyze_brand_queries is provided by the Google Search Console MCP server (lionkiii/google-searchconsole-mcp). 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 →