gsc_submit_sitemap

사이트맵을 Search Console에 제출(또는 재제출)해 재크롤을 유도. webmasters read-write 스코프 필요.

Server Mimi Seed @yoonion/mimi-seed-mcp
Category Write
Risk class Medium
Parameters 00 required

What gsc_submit_sitemap does on Mimi Seed

AI agents use gsc_submit_sitemap to create or update resources in Mimi Seed — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mimi Seed environment.

Why gsc_submit_sitemap needs a policy

This tool creates/modifies data by submitting a sitemap to Google Search Console, which reversibly updates indexing instructions. While it triggers external operations (Google's crawlers), the primary action is write-like (submitting/updating configuration). It does not delete data, execute arbitrary code on the user's infrastructure, or move money.

From the tool's definition Tool description states '제출(또는 재제출)' (submit or resubmit) and 'webmasters read-write 스코프 필요' (requires webmasters read-write scope). The action of submitting a sitemap to Google Search Console modifies Search Console state and triggers crawling operations.

Questions about gsc_submit_sitemap

What does the gsc_submit_sitemap tool do? +

사이트맵을 Search Console에 제출(또는 재제출)해 재크롤을 유도. webmasters read-write 스코프 필요. It is categorised as a Write tool in the Mimi Seed MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gsc_submit_sitemap? +

Register the Mimi Seed MCP server in PolicyLayer and add a rule for gsc_submit_sitemap: 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 Mimi Seed. Nothing to install.

What risk level is gsc_submit_sitemap? +

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

Can I rate-limit gsc_submit_sitemap? +

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

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

gsc_submit_sitemap is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

gsc_submit_sitemap is one line of Mimi Seed's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.