google-search-console.query_search_analytics

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Low RISK CLASS

Category Read

Parameters 92 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/google-search-console.query-search-analytics.md

WHAT IT DOES

What google-search-console.query_search_analytics does on Vee3

AI agents call google-search-console.query_search_analytics to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`end_date`	string	Yes	Inclusive range end date in YYYY-MM-DD format.
`site_url`	object	—	Optional property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from t
`row_limit`	object	—	Maximum number of rows to return. Defaults to 1000.
`start_row`	object	—	Zero-based row offset for pagination. Defaults to 0.
`data_state`	object	—	Whether to return only finalized data, all available daily data, or hourly data. Use hourly_all when grouping by hour. Defaults to final.
`dimensions`	object	—	Optional dimension names to group results. Supported values: date, query, page, country, device, searchAppearance, hour. Grouping by hour uses the hourly feed.
`start_date`	string	Yes	Inclusive range start date in YYYY-MM-DD format.
`search_type`	object	—	Search type filter. Defaults to web.
`dimension_filter_groups`	object	—	Optional filter groups matching the Google Search Console Search Analytics API shape. Each group contains filters that restrict which rows are returned.

Parameters from the server's own tool schema.

RISK

Why google-search-console.query_search_analytics is rated Low

Retrieves analytics data without modifying, deleting, or executing external operations.

From the tool's definition Query Search Console search analytics for verified property; returns performance rows.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google-search-console.query_search_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-search-console.query_search_analytics, this is the rule to start with:

google-search-console.query_search_analytics Allowed

google-search-console.query_search_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google-search-console.query_search_analytics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-search-console.query_search_analytics call is checked against it from then on.

FAQ

Questions about google-search-console.query_search_analytics

What does the google-search-console.query_search_analytics tool do? +

Query Search Console search analytics for a verified property. Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response. Returns performance rows with clicks, impressions, CTR, and average position, grouped by the requested dimensions. Daily search analytics typically lag by two to three days. For the Search Console last-24-hours hourly view, group by hour; those rows can include partial hours and cover up to ten days. Cost = 20 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.

What parameters does google-search-console.query_search_analytics accept? +

google-search-console.query_search_analytics accepts 9 parameters: end_date, site_url, row_limit, start_row, data_state, dimensions, start_date, search_type, dimension_filter_groups. Required: end_date, start_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on google-search-console.query_search_analytics? +

Register the Vee3 MCP server in PolicyLayer and add a rule for google-search-console.query_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 Vee3. Nothing to install.

What risk level is google-search-console.query_search_analytics? +

google-search-console.query_search_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google-search-console.query_search_analytics? +

Yes. Add a rate_limit block to the google-search-console.query_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.

How do I block google-search-console.query_search_analytics completely? +

Set action: deny in the PolicyLayer policy for google-search-console.query_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.

What MCP server provides google-search-console.query_search_analytics? +

google-search-console.query_search_analytics is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 269 Vee3 tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →