inspect_url
Inspect a URL in Google Search Console — check indexing status, crawl errors, mobile usability, and rich results. Use for technical SEO audits, diagnosing why pages aren't appearing in search, or checking mobile-friendliness.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/inspect-url.md
What inspect_url does on Freedom Mcp
AI agents call inspect_url to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
site_url | string | Yes | The site URL as shown in Search Console (e.g., "sc-domain:getfreedomos.com" or "https://getfreedomos.com/") |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
inspection_url | string | Yes | The full URL to inspect (e.g., "https://getfreedomos.com/features") |
Parameters from the server's own tool schema.
Why inspect_url is rated Low
This tool queries Google Search Console for diagnostic and reporting information about a URL's indexing and technical SEO status. It retrieves data without modifying, deleting, executing code, or triggering external state changes. No financial or destructive operations are possible. The blast radius of misuse is minimal—worst case an agent repeatedly queries the same URL, but this is a read operation only.
From the tool's definition 'Inspect a URL in Google Search Console — check indexing status, crawl errors, mobile usability, and rich results.' The verb 'inspect' and 'check' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs inspect_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_url, this is the rule to start with:
inspect_url is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every inspect_url call is checked against it from then on.
Questions about inspect_url
Inspect a URL in Google Search Console — check indexing status, crawl errors, mobile usability, and rich results. Use for technical SEO audits, diagnosing why pages aren't appearing in search, or checking mobile-friendliness. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
inspect_url accepts 3 parameters: site_url, companyId, inspection_url. Required: site_url, companyId, inspection_url. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom 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 Freedom Mcp. 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 Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue