Low Risk

search_console_analytics_query

Query the Search Console Search Analytics API for organic

How to control search_console_analytics_query ↓

What search_console_analytics_query does on Mureo

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

Low Risk

Why search_console_analytics_query needs a policy

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.

Documented attack patterns abuse exactly the kind of access search_console_analytics_query gives an agent:

How to control search_console_analytics_query

PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for search_console_analytics_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_console_analytics_query": {}
  }
}

search_console_analytics_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mureo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Mureo tool call.

Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.