get_sitemaps
List all sitemaps submitted to Google Search Console for a property — shows submission status, indexing coverage, errors, and warnings. Use for technical SEO audits and crawl coverage analysis.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-sitemaps.md
What get_sitemaps does on Freedom Mcp
AI agents call get_sitemaps 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 exactly as shown in Search Console (e.g., "sc-domain:example.com" or "https://example.com/") |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why get_sitemaps is rated Low
get_sitemaps retrieves and displays information about sitemaps from Google Search Console. It performs no mutations, executions, or destructive actions. The tool is informational only, supporting technical SEO audits through read-only queries. No side effects or irreversible changes occur.
From the tool's definition Tool description explicitly states 'List all sitemaps' and 'shows submission status, indexing coverage, errors, and warnings' — purely retrieval operations with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_sitemaps 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 get_sitemaps, this is the rule to start with:
get_sitemaps 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 get_sitemaps call is checked against it from then on.
Questions about get_sitemaps
List all sitemaps submitted to Google Search Console for a property — shows submission status, indexing coverage, errors, and warnings. Use for technical SEO audits and crawl coverage analysis. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_sitemaps accepts 2 parameters: site_url, companyId. Required: site_url, companyId. 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 get_sitemaps: 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.
get_sitemaps 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 get_sitemaps 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 get_sitemaps. 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.
get_sitemaps 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