search_analytics
AI agents call search_analytics to retrieve information from Google Search Console Mcp Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves search performance data from Google Search Console. Although the description is empty, the name 'search_analytics' combined with the server's stated purpose ('querying search analytics') and the context of sibling operations clearly indicates a data retrieval function.
From the tool's definition Tool is named 'search_analytics' and exists on a 'Google Search Console' MCP server that 'enables querying search analytics'. The server description emphasizes querying and inspection (read operations), not modification.
Attacks that exploit this kind of access
search_analytics. It is categorised as a Read tool in the Google Search Console Mcp Python MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console Mcp Python MCP server in PolicyLayer and add a rule for search_analytics: 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 Mcp Python. Nothing to install.
search_analytics 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 search_analytics 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 search_analytics. 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.
search_analytics is provided by the Google Search Console Mcp Python MCP server (locomotive-agency/google-search-console-mcp-python). 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 →