seo_submit_urls
Submit up to 500 URLs on a verified property to the search engine for (re)crawling, e.g. after publishing or updating a page. URLs must be under the property. Returns how many were submitted plus the remaining daily and monthly quota; the call is rejected up front when the batch exceeds the quota...
This record as markdown: /tools/com-getmunin-munin/seo-submit-urls.md
What seo_submit_urls does on Munin
AI agents invoke seo_submit_urls to trigger actions in Munin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why seo_submit_urls is rated High
Triggers external search engine crawl operations, an outbound action with external side effects.
From the tool's definition Submit up to 500 URLs to the search engine for (re)crawling
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs seo_submit_urls safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo_submit_urls, this is the rule to start with:
seo_submit_urls stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every seo_submit_urls call is checked against it from then on.
Questions about seo_submit_urls
Submit up to 500 URLs on a verified property to the search engine for (re)crawling, e.g. after publishing or updating a page. URLs must be under the property. Returns how many were submitted plus the remaining daily and monthly quota; the call is rejected up front when the batch exceeds the quota left, rather than partially submitting. Submissions count against a per-site daily cap, so submit only URLs whose content actually changed. Not every engine offers URL submission — Bing does, Google Search Console does not, and the call fails with a clear message for engines that don’t. It is categorised as a Execute tool in the Munin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Munin MCP server in PolicyLayer and add a rule for seo_submit_urls: 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 Munin. Nothing to install.
seo_submit_urls is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the seo_submit_urls 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 seo_submit_urls. 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.
seo_submit_urls is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
Across the catalogue