Export search analytics data as CSV or JSON format for external analysis or reporting.
AI agents call export_analytics 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 reads search analytics data from Google Search Console and exports it in a specified format (CSV or JSON). It does not modify, delete, or create any data. The export is a read operation with no side effects, making it a low-severity Read category tool.
From the tool's definition 'Export search analytics data as CSV or JSON format for external analysis or reporting' — purely retrieves and formats existing data with no side effects.
Attacks that exploit this kind of access
Export search analytics data as CSV or JSON format for external analysis or reporting. 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 export_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. Nothing to install.
export_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 export_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 export_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.
export_analytics 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 →