High Risk →

compare_performance

Compare search performance between two time periods. Shows which queries/pages gained or lost traffic.

Part of the Google Searchconsole MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke compare_performance to trigger processes or run actions in Google Searchconsole. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

compare_performance can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

google-searchconsole.yaml
tools:
  compare_performance:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Google Searchconsole policy for all 13 tools.

Tool Name compare_performance
Category Execute
Risk Level High

View all 13 tools →

Agents calling execute-class tools like compare_performance have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

compare_performance is one of the high-risk operations in Google Searchconsole. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the compare_performance tool do? +

Compare search performance between two time periods. Shows which queries/pages gained or lost traffic.. It is categorised as a Execute tool in the Google Searchconsole MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on compare_performance? +

Add a rule in your Intercept YAML policy under the tools section for compare_performance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Searchconsole MCP server.

What risk level is compare_performance? +

compare_performance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit compare_performance? +

Yes. Add a rate_limit block to the compare_performance rule in your Intercept 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 compare_performance completely? +

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

compare_performance is provided by the Google Searchconsole MCP server (google-searchconsole-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.