inspect_url
AI agents call inspect_url to retrieve information from Google Search Console Mcp Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
URL inspection in Google Search Console typically retrieves indexing status, crawl information, and other diagnostic metadata about a URL without modifying or executing anything. This is a read-only operation. The empty description lowers confidence slightly, but the server's stated capability to support URL inspection and the non-destructive nature of inspection queries support a Read classification.
From the tool's definition Tool name 'inspect_url' and server context (Google Search Console) suggest URL inspection/querying. The server description mentions 'inspecting URLs' as part of its capabilities. No description provided for the tool itself.
Attacks that exploit this kind of access
inspect_url. It is categorised as a Read tool in the Google Search Console Mcp Python MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console Mcp Python 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 Python. Nothing to install.
inspect_url 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 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.
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.
inspect_url is provided by the Google Search Console Mcp Python MCP server (locomotive-agency/google-search-console-mcp-python). 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 →