Inspect a URL to see if it is indexed or can be indexed
AI agents call index_inspect to retrieve information from Google Search Console MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs read-only inspection of URL indexing status. It retrieves information about Google Search Console's current index state for a given URL, with no side effects, data creation, modification, deletion, or execution of external operations. This aligns with the Read category definition of retrieving or querying data with no side effects.
From the tool's definition Tool description states 'Inspect a URL to see if it is indexed or can be indexed' — this is a query/inspection operation that retrieves indexing status without modifying any data.
Attacks that exploit this kind of access
Inspect a URL to see if it is indexed or can be indexed. It is categorised as a Read tool in the Google Search Console MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console MCP Server MCP server in PolicyLayer and add a rule for index_inspect: 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 Server. Nothing to install.
index_inspect is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the index_inspect 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.
Set action: deny in the PolicyLayer policy for index_inspect. 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.
index_inspect is provided by the Google Search Console MCP Server MCP server (sandriaas/mcp-server-gsc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →