Low Risk

inspect_url

Authoritative URL Inspection.

How to control inspect_url ↓

AI agents call inspect_url to retrieve information from Google Search Console MCP Intel Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves and queries URL inspection data from Google Search Console without creating, modifying, deleting, or executing any external operations. It falls squarely into the Read category as it gathers information for analysis. Severity is low because inspecting URL metadata poses minimal risk even if misused by an AI agent—it only exposes already-public indexing information.

From the tool's definition Tool named 'inspect_url' with description 'Authoritative URL Inspection' performs information retrieval about a URL's indexing and appearance status in Google Search Console.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console MCP Intel Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect_url:

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

inspect_url 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 Google Search Console MCP Intel Engine — 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.

Go deeper

What does the inspect_url tool do? +

Authoritative URL Inspection. It is categorised as a Read tool in the Google Search Console MCP Intel Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on inspect_url? +

Register the Google Search Console MCP Intel Engine MCP server in PolicyLayer and add a rule for inspect_url: 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 MCP Intel Engine. Nothing to install.

What risk level is inspect_url? +

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

Can I rate-limit inspect_url? +

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

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

inspect_url is provided by the Google Search Console MCP Intel Engine MCP server (surendranb/google-search-console-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Search Console MCP Intel Engine tool call.

Deterministic rules across all 14 Google Search Console MCP Intel Engine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

14 Google Search Console MCP Intel Engine tools catalogued and risk-classified — across an index of 42,500+ 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.