rebuild_sitemap

Rebuild the whole sitemap (async background job).

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/rebuild-sitemap.md

WHAT IT DOES

What rebuild_sitemap does on Webcake Storefront

AI agents invoke rebuild_sitemap to trigger actions in Webcake Storefront. 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.

RISK

Why rebuild_sitemap is rated High

This tool triggers an asynchronous background job that regenerates the entire sitemap. It executes an external operation with side effects (rebuilding/overwriting the sitemap), making it Execute category. While it overwrites the sitemap, sitemaps are typically regeneratable artifacts rather than irreplaceable data, so it doesn't rise to Destructive.

From the tool's definition Rebuild the whole sitemap (async background job)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rebuild_sitemap safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rebuild_sitemap, this is the rule to start with:

rebuild_sitemap Rate-limited

rebuild_sitemap 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rebuild_sitemap": {
      "limits": [
        {
          "counter": "rebuild_sitemap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every rebuild_sitemap call is checked against it from then on.

FAQ

Questions about rebuild_sitemap

What does the rebuild_sitemap tool do? +

Rebuild the whole sitemap (async background job). It is categorised as a Execute tool in the Webcake Storefront MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rebuild_sitemap? +

Register the Webcake Storefront MCP server in PolicyLayer and add a rule for rebuild_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 Webcake Storefront. Nothing to install.

What risk level is rebuild_sitemap? +

rebuild_sitemap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rebuild_sitemap? +

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

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

rebuild_sitemap is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →