submit_sitemap_tool · MCP Google Search Console MCP

WHAT IT DOES

What submit_sitemap_tool does on MCP Google Search Console

AI agents use submit_sitemap_tool to create or update resources in MCP Google Search Console — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Search Console environment.

WHY IT NEEDS A POLICY

Why submit_sitemap_tool needs a policy

Submitting a sitemap is a reversible operation that instructs Google's crawler to index specified URLs. It creates a new configuration entry in Search Console but does not irreversibly delete data, execute arbitrary code, or commit financial transactions. The blast radius is low—it directs crawling to specified URLs which is a normal, recoverable SEO operation.

From the tool's definition Tool name 'submit_sitemap_tool' and description 'Submit a sitemap for crawling' indicate an action that creates or registers a new sitemap configuration with Google Search Console, modifying the indexing directives without deleting or overwriting existing…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_sitemap_tool Rate-limited

submit_sitemap_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_sitemap_tool": {
      "limits": [
        {
          "counter": "submit_sitemap_tool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Google Search Console, so you can run agents against it safely.

FAQ

Questions about submit_sitemap_tool

What does the submit_sitemap_tool tool do? +

Submit a sitemap for crawling. It is categorised as a Write tool in the MCP Google Search Console MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_sitemap_tool? +

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

What risk level is submit_sitemap_tool? +

submit_sitemap_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_sitemap_tool? +

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

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

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