find_keyword_opportunities

Find keyword optimization opportunities - queries with high impressions but low CTR that could be improved.

Server Google Search Console lionkiii/google-searchconsole-mcp
Category Read
Risk class Low
Parameters 00 required

What find_keyword_opportunities does on Google Search Console

AI agents call find_keyword_opportunities 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.

Why find_keyword_opportunities needs a policy

This tool retrieves and analyzes search analytics data to identify optimization opportunities. It performs no write operations (does not modify Search Console settings), no destructive actions, no code execution, and no financial transactions. It is fundamentally a read/query operation that extracts insights from existing search performance data.

From the tool's definition Tool description states it 'Find[s] keyword optimization opportunities' by analyzing 'queries with high impressions but low CTR' — purely analytical/retrieval of existing Search Console metrics without modifying, deleting, or executing external actions.

Questions about find_keyword_opportunities

What does the find_keyword_opportunities tool do? +

Find keyword optimization opportunities - queries with high impressions but low CTR that could be improved. It is categorised as a Read tool in the Google Search Console MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_keyword_opportunities? +

Register the Google Search Console MCP server in PolicyLayer and add a rule for find_keyword_opportunities: 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.

What risk level is find_keyword_opportunities? +

find_keyword_opportunities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_keyword_opportunities? +

Yes. Add a rate_limit block to the find_keyword_opportunities 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.

How do I block find_keyword_opportunities completely? +

Set action: deny in the PolicyLayer policy for find_keyword_opportunities. 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.

What MCP server provides find_keyword_opportunities? +

find_keyword_opportunities 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.