search_console_analytics_query

Query the Search Console Search Analytics API for organic

SERVERMureo SOURCElogly/mureo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/logly-mureo/search-console-analytics-query.md

WHAT IT DOES

What search_console_analytics_query does on Mureo

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

RISK

Why search_console_analytics_query is rated Low

This tool retrieves analytics data from Google Search Console's Search Analytics API. It performs a read-only operation — querying metrics about organic search performance. There are no side effects, no data modification, no code execution, and no destructive or financial operations.

From the tool's definition Tool name contains 'query' and description states 'Query the Search Console Search Analytics API for organic' — indicates data retrieval from Search Console analytics without modification or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_console_analytics_query safely

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

search_console_analytics_query Allowed

search_console_analytics_query 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": {
    "search_console_analytics_query": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mureo, apply this rule, and every search_console_analytics_query call is checked against it from then on.

FAQ

Questions about search_console_analytics_query

What does the search_console_analytics_query tool do? +

Query the Search Console Search Analytics API for organic. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_console_analytics_query? +

Register the Mureo MCP server in PolicyLayer and add a rule for search_console_analytics_query: 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 Mureo. Nothing to install.

What risk level is search_console_analytics_query? +

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

Can I rate-limit search_console_analytics_query? +

Yes. Add a rate_limit block to the search_console_analytics_query 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 search_console_analytics_query completely? +

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

search_console_analytics_query is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mureo, and thousands of servers like it.

This server

All 225 Mureo tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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